You may attack the targets: the scenario instances served under pwnstamp-targets.dev, and nothing else.

user	The account the target app runs as. In scope.
root	Root inside the target container. In scope.
host	The VM around the container. Not yet in scope; planned.

Out of scope: the platform (reverse proxy, scenario host, Firecracker, the network), these sites, the signer, the hosting provider's infrastructure, and any other player. Denial of service against any of them is out of scope too.

• Shared. Every player attacks the same instance at the same time. Anything you leave on it is visible to the others, and anyone at your level can undo your work.
• Short-lived. Each instance is rebuilt from scratch every hour; nothing survives a rotation.
• No egress. Targets cannot reach the internet or each other: no reverse shells, no downloads from inside. Bring everything in through the target's own surface.
• Reproducible. Each scenario page gives the exact images, sources and VM. Research against your own copy; use the hosted target to confirm a finding and sign.

• Sign with /run/pwnstamp/bin/pwnstamp sign <pseudo> at the level you reached. The pseudo is public and declarative: pwnstamp doesn't know who you are.
• A proof says that someone holding the level's key signed that pseudo during that hour. It says nothing about how.
• Keys of another level are not yours to publish: leaking a key lets others sign without the access.

• Don't use a target to host content for others (phishing, malware, defacement).
• Don't degrade the instance on purpose for other players.
• Found a way out of scope (into the platform, or another target)? Report it, don't use it.

Abuse and security contact: abuse@pwnstamp.org

ScenariosEvery scenario, current and superseded→ RulesScope, no egress, shared machine, abuse contact→ Verify a proofverify.pwnstamp.org→