Minting Out of Thin Air: The LayerZero Delegate Hijack, Explained

Security firm Blockaid flagged automated minting of The Sandbox's SAND token on Base this month — hundreds of transactions producing tokens with nothing behind them, after an attacker gained control of delegate permissions in the token's LayerZero cross-chain configuration.

The mechanism is worth understanding, because it will recur. Cross-chain tokens are an accounting trick: the "real" supply lives on one chain, and bridged versions elsewhere are IOUs minted and burned by messaging infrastructure. In LayerZero's model, a token's team designates a delegate — an address with authority over that messaging configuration. Control the delegate, and you can tell the destination chain that deposits happened which never did. The contract obeys; unbacked tokens appear.

Not a token bug

Nothing in SAND's own contract failed. That's the uncomfortable part: audits of the token tell you nothing about this class of risk, which lives in the permissions wrapped around the bridge. It echoes every major bridge failure since Wormhole and Ronin — the chain of custody is only as strong as its most powerful key, and the industry keeps rediscovering how many powerful keys exist off the audit reports.

The automation footnote

Blockaid's telemetry showed the minting run as scripted — hundreds of transactions at machine tempo. Exploits are increasingly executed end-to-end by software the moment access lands, which shrinks the response window from days to minutes. The month's broader theme, again: the attacker tempo is now machine tempo.