Kompromat
kompromat.sh- Category
- Cybersecurity
- Rank
- No. 4213Tools index
- Pricing
- Open Source
- Type
- TOOL
- Date
About
Kompromat is an open-source protocol and CLI for capture-the-flag and red-team exercises. A defender generates a key file and plants it in their infrastructure, and anyone who finds it can submit a signed Schnorr proof of possession without exposing the secret. Each report opens a dossier where finder and defender exchange encrypted notes, backed by a small HTTP API on SQLite that stores only ciphertext.
At a glance
Kompromat is an MIT-licensed Rust command-line tool and small HTTP API for capture-the-flag and red-team exercises on your own infrastructure. You generate a key file and plant a copy somewhere, such as a backup. Whoever finds it submits a signed proof that they hold it, which opens a dossier where the finder and the defender exchange end-to-end encrypted notes.
Good fit
A defender who wants proof that someone actually reached a specific location, like a tenant export or a backup, rather than a bug report claiming it. It fits scoped bounty-style briefs and red-team engagements, and the site offers ready-made prompts for agents playing the defender or red-teamer side.
Consider something else when
You need a full CTF platform with scoring, teams, challenge hosting or alerting. Kompromat only proves possession of a planted key and carries notes. Reading the key file itself is silent, so it will not tell you when someone opened it, only when they report it.
Start here
With Rust installed, run cargo install --locked --path . from the repository and start kompromat-api. In a private directory run kompromat generate --out flag.json --manifest-out manifest.json, then kompromat register manifest.json. Keep defender.json, plant a copy of flag.json, and test the loop with kompromat report flag.json --hunt "$HUNT_URL" --message 'Found in the backup'.
Cost and requirements
Open source under the MIT license. The project runs a public endpoint at kompromat.sh, or you can self-host the API, which stores data in SQLite. Building needs Rust. The commands default to http://127.0.0.1:3000; a remote hunt needs an HTTPS reverse proxy in front of the API and its URL passed with --api to both generate and register.
Limits to know
The server never sees secret keys or readable notes, but the manifest metadata is public, and anyone with the hunt URL can see dossier IDs, report arrival times, which side sent each note and its size. Losing the defender key or a finder's dossier key loses access to those notes. The project is young, with 12 commits and no published releases, and the author describes a public capture-the-flag game at kompromat.sh as planned rather than running.
Still unclear
- Does the public kompromat.sh endpoint have usage limits, retention terms or any cost?
Sources checked 2026-11-17. Source-based assessment.
Tags
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.