Small teams get the same phishing emails as big companies, without a security team to ask. "Is this invoice safe to open?" usually gets answered by opening it.
Burn Box answers it for them, and nobody has to open anything. Forward the suspicious email to Burn Box, or drop in a file or a link. Even reading the email happens inside a sealed box: Burn Box checks who really sent it, whether the sender's domain vouched for it, where replies really go, and whether its links lie about where they lead. Then it splits the email up. Every link and every attachment gets a fresh box of its own, running side by side.
For each part, Burn Box seals a fresh container on a cloud VM: no network, a read-only system, no privileges, strict CPU, memory, process and time limits, and gVisor as a second kernel wall. It plants fake secrets inside (a cloud key, a crypto wallet, a password file) whose only job is to be reached for. Then it detonates the sample. Files run under strace, and links open in headless Chromium on a private lab network. Every file touch, process, connection attempt and form submission streams live to the screen. When the run ends, the box is destroyed and its removal confirmed.
The model reads the behavioural record and writes the verdict in plain English: what the sample pretended to be, what it actually tried, which canaries it reached for, how many escape attempts the wall stopped, and safe, suspicious or malicious with reasons. A rules floor from the evidence sets the minimum verdict; the model can raise it but never lower it, so a sample cannot talk its way to a softer verdict. If the model is unreachable, the rules verdict stands and the receipt says so honestly.
Every run ends with a signed receipt (Ed25519): the container, the limits applied, the canaries and the destroyed-at time. Receipts are publicly verifiable: a public verification page lets anyone paste or upload a receipt and check the signature, in the browser and on the server.
Burn Box keeps a verdict history with team workspaces (a team shares runs through an unguessable code, no accounts, and team runs stay off the public list), offers a link-only quick check for "is this URL safe?" moments, and provides a public receipt verification page.
The demo is an "invoice overdue" email with two traps, forwarded to Burn Box unopened. The envelope box finds a spoofed sender (SPF, DKIM and DMARC fail), a reply-to address on a lookalike domain, and a link whose text lies about where it goes. Then two more boxes open. The attachment reads the planted cloud key and wallet, tries to send them home, tries to install itself and tries to delete shared files, and is blocked at every step. The link is a fake sign-in page. Burn Box types a fake login into it and traces the details to a collector on a different site. No human approval is needed, because nothing real is ever entered. Three boxes, three burns, one verdict: Malicious, delete it without opening anything.
The containment moment is the product. Burn Box does dangerous work that is only safe because of the box, and it shows the box holding in real time.
How it was built with Kiro
Burn Box's Kiroween build was developed spec-first in Kiro, and the repository carries the evidence: a /.kiro directory at the root with steering documents (product, tech, structure) and five feature specs, each with requirements, design and task files.
- Live inference: wiring the model's verdicts into the detonation engine, with the source of every verdict labelled (model or rules) and named on its receipt.
- Verdict history and team workspace: shared run history behind unguessable team codes, with tests proving team runs never leak into the public list.
- Link-only quick check: a one-field URL check that produces the same signed receipt as a full run.
- Receipt verification: a public page and API that verify Ed25519 receipt signatures. Building it surfaced and fixed a real bug: file and link receipts were signed over a field JSON drops on download, so they could never verify.
- Host deploy: a spec'd, volume-preserving deployment to the live demo host, written as requirements, design and tasks before any command ran.
Each spec's tasks were worked in their own Kiro session, and the suite stayed green throughout: typecheck passes and 31 tests pass, including new tests for teams, quick checks and receipt verification. The specs also drove two production fixes after deployment: a file-permissions failure in the deploy script, and a model retirement (the originally specified model was withdrawn for new API keys; the build now runs on its verified successor, and the specs were updated to match reality).
Built With
- chromium
- cloud
- docker
- ed25519
- events
- gvisor
- kiro
- node.js
- playwright
- python
- server-sent
- strace
- typescript
