Scenario: self-replicating loader in @defuse-sandbox

defuse-sandbox

Local scenario · modeled services and simulated timings.

Revoke everything, or defuse it

The same incident, run two ways against the worm's published triggers. On the left, the naive "revoke it all now" baseline. On the right, Defuse's safe order. Step through, or press play.

step 1/6

Naive: revoke everything now

detonated

/srv/defuse-sentinel

destroyed

L0 9 actions
- Quarantine @defuse-sandbox/strings@2.4.1
- Remove planted hooks from defuse-sandbox/app-b
- Revoke old strings-publish
- Revoke old hook-bot
- Revoke old release-bot
- Rotate SENTRY_AUTH_TOKEN
- Rotate strings-publish
- Rotate hook-bot
- Rotate release-bot
Revocation handler watcher:defuse-runner-1:defuse-watcher.service saw 3 watched secret(s) fail while host:defuse-runner-1 was up
Dead-man’s switch host:defuse-runner-1 lost publish and source access in the same step

Defuse: safe order

contained

/srv/defuse-sentinel

intact

L0 5 actions
- Isolate host defuse-runner-1
- Pause runner sandbox-persistent
- Quarantine @defuse-sandbox/strings@2.4.1
- Block writes by agent duo-developer-flow
- Rotate release-bot