Contract Analyzer

The dispatcher maps selector 0x23b872dd to the transferFrom entry at runtime offset 0x02b8. That entry obtains msg.sender through the helper at 0x0472, calls the internal routine at 0x048b, and conditionally skips the allowance-spending routine at 0x04f5 when the internal routine returns true. Inside the 0x048b routine, the runtime embeds the exact 20-byte value 0x36e9a317bdfa224fde58eeb7fadc442bd8ad126c, masks it as an address, compares it with the supplied caller/spender value, preserves that comparison result, and then calls the token-transfer routine at 0x0587. The transfer routine validates nonzero endpoints and invokes the balance-update routine at 0x0846. At 0x0846, the source balance is loaded and checked against the amount, reduced with SSTORE, the destination balance is increased with SSTORE, and the standard Transfer topic 0xddf252ad… is logged. Control then returns to the transferFrom entry. If the saved caller comparison is true, the conditional jump at approximately 0x02df bypasses the call to 0x04f5, so no allowance is checked or reduced; the external function then returns boolean true. For all other callers, control reaches 0x04f5, which loads allowance[from][caller], accepts the maximum-uint sentinel as infinite approval, otherwise checks that allowance is at least the amount, and invokes the allowance-writing routine at 0x0677 to subtract it. Lutetia captures this ordering and the exact hard-coded caller, although its displayed 'return amount' is a decompiler type/stack-recovery error: the outer runtime path explicitly pushes 1 before returning, consistent with the ERC-20 boolean return. Heimdall accurately recovers the ordinary transfer balance mutations but decompiles selector 0x23b872dd only as an argument-validation stub, so its output is incomplete for the decisive function rather than contrary evidence. The selector table, embedded address scan, Lutetia branch, and raw runtime control flow independently converge on the same privileged allowance bypass. The current token runtime contains no administrator setter or revocation path for this address among its nine dispatched selectors, making the privilege hard-coded in this deployed code. Because the bypass is in transferFrom and applies to arbitrary nonzero source and destination addresses subject only to source balance sufficiency, the privileged operator can move holder balances without holder approval. The evidence does not establish that routine holder transfers fail, that a router or pair is specially blacklisted, or that an exact DEX sell path is blocked.