01 Blast radius
Real customer path
waitingLatency is sampled by the customer-traffic sidecar hitting the neighbor victim-checkout. Even when the attacker lab steals CPU or memory, this signal originates from a separate container so blast radius is observable end-to-end.
Prepare mock customers, verify default Docker evidence, and reset chaos payloads without leaving the browser.
No result yet.
A diagnostic endpoint passes input to ping through the shell. CVE-backed pattern: TP-Link CVE-2023-1389, Cisco CVE-2023-20231, Palo Alto CVE-2024-3400, and Ivanti CVE-2024-21887.
No result yet.
Write a harmless marker into /app/uploads. On the Linux host it appears as UID/GID 0:0 because userns remap is off.
No result yet.
Simulate malware-style collection: sample customer files, invoice files, and reachable Postgres rows from the compromised app network.
No result yet.
Encrypt 200 mock customer files with a reversible payload. This is the honest impact: total app/data compromise without claiming host shell.
No result yet.
Probe victim-checkout directly to confirm the neighbor service is healthy before pressure payloads run.