But there was a SSTORE in an admin function that allowed toggling a boolean flag — and that flag was used in another function to compute a jump offset via JUMPI . With a specific storage layout, that flag could point to the dead JUMPDEST .
Result: "Dead code" becomes a self-destruct backdoor after a storage collision. 0xdeadcode
April 13, 2026
One storage write to flip the false to true later, and pause becomes owner-only backdoor. But there was a SSTORE in an admin
Since "0xdeadcode" evokes low-level programming, EVM (Ethereum Virtual Machine) internals, security exploits, and perhaps a bit of rebellious cypherpunk energy, I'll write two versions: EVM (Ethereum Virtual Machine) internals
Then I traced the JUMPDEST that should be unreachable — but a storage collision could reanimate it.