April 13, 2026
Last week I audited a contract with 14% unreachable instructions. The owner swore they were "leftover from testing." 0xdeadcode
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: April 13, 2026 Last week I audited a
Result: "Dead code" becomes a self-destruct backdoor after a storage collision. A short blog/forum post exploring a "dead code"
(thread-style) 2. A short blog/forum post exploring a "dead code" vulnerability in smart contracts 1. X (Twitter) Post by @0xdeadcode Main post: 0xdeadcode
One storage write to flip the false to true later, and pause becomes owner-only backdoor.
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 .
April 13, 2026
Last week I audited a contract with 14% unreachable instructions. The owner swore they were "leftover from testing."
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:
Result: "Dead code" becomes a self-destruct backdoor after a storage collision.
(thread-style) 2. A short blog/forum post exploring a "dead code" vulnerability in smart contracts 1. X (Twitter) Post by @0xdeadcode Main post: 0xdeadcode
One storage write to flip the false to true later, and pause becomes owner-only backdoor.
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 .