Worked example · 2026-06

TesseraDAO ($TSR) — admin-key compromise → unauthorised mint-and-dump — 2026-06-01

Loss: ~$2.4M–$2.5M realised. The attacker used a compromised privileged key to mint ~99,000,000 TSR on BNB Chain with no corresponding backing, then immediately swapped the freshly-minted supply into ~$2.5M USDT against on-chain liquidity, collapsing TSR ~99%. Proceeds were bridged to Ethereum, where ~1,285.5 ETH was laundered through Tornado Cash. As with all admin-key mint-and-dump events, the nominal mint (99M TSR) is bounded only by the contract's data type, while the realised proceeds (~$2.5M) are bounded by AMM liquidity depth at the dump moment — the same notional-vs-realised gap OAK records for Holograph and MAP Protocol.
OAK Techniques observed: OAK-T11.002 (Wallet-Software / Signing-Surface Compromise, operator-side deployer/minter-key sub-class — the proximate cause was loss of control of a privileged key that retained mint/owner authority over the TSR token contract. PeckShield and on-chain analysts attribute the event to private-key leakage / ownership takeover, not a contract-logic bug. See techniques/T11.002-wallet-software-distribution-compromise.md). OAK-T9.004 (Access-Control Misconfiguration — the structural precondition: the TSR contract retained an open mint capability under a single privileged key with no mint-cap, timelock, or multisig, so a key compromise converted directly into an unlimited mint. The function's access control was correct in the narrow sense — only the key-holder could mint — but lacked the secondary circuit-breakers that bound the blast radius of a compromise, the Resolv Labs "single key with no circuit-breakers" sub-class. See techniques/T9.004-access-control-misconfiguration.md). OAK-T5.001 (Hard-LP-Drain / downstream dump — the realised-extraction mechanism: the minted TSR was sold against on-chain liquidity for USDT, draining the pool. See techniques/T5.001-hard-lp-drain.md). OAK-T7.001 (Mixer-Routed Hop — ~1,285.5 ETH laundered through Tornado Cash after bridging BNB Chain → Ethereum. See techniques/T7.001-mixer-routed-hop.md). The combination T11.002 + T9.004 + T5.001 + T7.001 is the canonical OAK pattern for operator-key-compromise → unlimited-mint → AMM-dump → mixer incidents.
Attribution: pseudonymous attacker; on-chain addresses identified by PeckShield, not linked to a named individual or group. The mint transaction is timestamped 2026-06-01 11:38:25 UTC. The leak vector (phishing, insider, infrastructure breach, or plaintext key storage) was not publicly disclosed at the time of writing.
Key teaching point: TesseraDAO is a 2026 re-anchor of the Holograph pattern: a token contract that retained an unbounded mint authority under a single operator key, where the compromise of that key converted directly into an unlimited mint, an AMM dump, and a mixer cash-out. The lesson is not "protect the key better" alone — keys will be compromised — but "design the mint function so that a compromised key cannot mint without limit." A mint-cap per transaction/epoch, an oracle/collateral check on mint legitimacy, a timelock on supply-affecting calls, or a multisig on the minter role would each have bounded the loss to a fraction of the ~$2.5M realised. The corpus already carries this lesson at Resolv Labs (USR, $25M, 2026-03) and Holograph (HLG, $14.4M, 2024-06); TesseraDAO is the smaller-cap BNB-Chain restatement, confirming the pattern is not memecoin-specific but a general property of any token that ships unbounded mint authority behind a single key.

Summary

TesseraDAO is a DeFi project on BNB Chain whose TSR token contract retained a privileged mint/owner capability. On 2026-06-01 at 11:38:25 UTC, an attacker in control of that privileged key minted ~99,000,000 TSR directly to an attacker-controlled address, with no corresponding deposit, lock, or collateral.

The attacker immediately sold the minted supply into on-chain liquidity, realising ~$2.5M USDT before the market repriced TSR to near zero (~99% drawdown). The realised figure is far below the nominal mint because the unbacked tokens could only be exited against available pool depth — the structural signature of a mint-and-dump. The attacker then bridged the proceeds from BNB Chain to Ethereum and laundered ~1,285.5 ETH through Tornado Cash.

PeckShield and on-chain analysts classified the root cause as private-key leakage / ownership takeover — a custody/signing failure at the operator key layer — rather than a smart-contract logic flaw. The exploitable precondition, however, was a contract-design choice: the mint function had no cap, no timelock, and no multisig, so a single compromised key translated into an effectively unbounded supply event.

Why this is structurally significant

T11.002 (operator-side deployer/minter-key compromise) and T9.004 (open mint capability) compose into OAK's canonical admin-key-mint-and-dump shape, and TesseraDAO is a clean restatement of it:

The key compromise (T11.002) is the proximate cause. OAK's defender position is that operator key compromise is endemic and should be treated as a when, not an if — so the technique's mitigation weight sits on blast-radius limiters, not solely on key hygiene.
The missing circuit-breakers (T9.004) are the load-bearing design defect. This is the Resolv Labs sub-class: "a single privileged key with no secondary safety mechanisms (oracle check, mint cap, timelock) converts a key compromise directly into an unlimited-mint exploit." TesseraDAO's mint had no ceiling, so the only limit on extraction was downstream liquidity.
The AMM dump (T5.001) sets the realised loss. The 99M-TSR nominal mint is bounded by the uint type; the ~$2.5M realised is bounded by pool depth at the dump moment. Contributors should always record both numbers — the notional supply event and the realised proceeds — because the gap is the defining feature of the class and the basis for the "liquidity depth is the realised-loss bound" defender lesson.
The mixer hop (T7.001) is the cash-out. Bridging BNB Chain → Ethereum and routing ~1,285.5 ETH through Tornado Cash is the standard laundering tail for these events and mirrors Holograph exactly.

Against the 2026 cohort, TesseraDAO is the small-cap BNB-Chain restatement of a pattern OAK has now anchored at three scales: Resolv ($25M, stablecoin), Holograph ($14.4M, mid-cap ERC-20), TesseraDAO (~$2.5M, BNB-Chain token). The consistency across scales is the point — the defect is architectural (unbounded mint behind one key), not a property of any particular market cap or chain.

Timeline (UTC)

When	Event	OAK ref
Pre-2026-06-01	TSR token contract on BNB Chain retains an open mint/owner capability under a single privileged key, with no mint-cap, timelock, or multisig on the minter role	(standing T9.004 surface)
2026-06-01 11:38:25	Attacker (in control of the compromised privileged key) mints ~99,000,000 TSR to an attacker-controlled address with no backing	T11.002 + T9.004 execution
2026-06-01	Attacker dumps the minted TSR into on-chain liquidity for ~$2.5M USDT; TSR craters ~99%	T5.001 extraction
2026-06-01	Proceeds bridged from BNB Chain to Ethereum; ~1,285.5 ETH laundered through Tornado Cash	T7.001 laundering
2026-06-01	PeckShield / on-chain analysts flag the incident as private-key leakage / ownership takeover (~$2.4M–$2.5M)	(third-party detection)

What defenders observed

Pre-event (contract design): the TSR mint function was reachable by a single key with no ceiling. A mint-cap (per-tx / per-epoch), a collateral/oracle precondition on mint, a timelock on supply-affecting calls, or a multisig minter role would each have bounded the loss. Defender lesson: treat retained mint authority as a first-class risk surface and require at least one blast-radius limiter on it regardless of how well the key is protected.
At-event (on-chain signal): a single transaction minting ~99M TSR — implausibly large relative to historical supply, with no matching deposit/lock — is the direct exploitation signature. A supply-monitoring indicator (mint magnitude vs historical supply; mint with no corresponding collateral event) would have fired immediately. This is the same mint-magnitude signal anchored at MAP Protocol and Resolv.
At-event (market signal): the ~99% TSR drawdown within minutes is the market pricing the dilution; by the time price reflects it, the exit is largely complete. Price collapse is a confirmation, not an early signal — the mint event itself is the early signal.
Post-event (laundering): bridge BNB Chain → Ethereum followed by Tornado Cash is the standard tail; the ~1,285.5 ETH figure is the laundering throughput, not necessarily the full realised proceeds. Defender lesson: track the bridge-then-mixer route as the canonical cash-out for BNB-Chain token exploits.

What this example tells contributors writing future Technique pages

Record the notional-vs-realised gap explicitly. 99M TSR nominal mint vs ~$2.5M realised is the defining shape of mint-and-dump; the gap is the liquidity-depth bound. Always log both figures, as OAK does for Holograph and MAP.
Map the full four-leg chain. Operator-key-compromise mint-and-dump incidents are T11.002 + T9.004 + T5.001 + T7.001, not a single technique. The key compromise is proximate, the missing circuit-breakers are load-bearing, the AMM dump sets realised loss, and the mixer is the cash-out. Mirror the Holograph mapping.
The lesson is circuit-breakers, not key hygiene alone. When the root cause is "single key with unbounded mint," the technique guidance should foreground mint-cap / oracle-check / timelock / multisig as the blast-radius mitigations, because key compromise is treated as inevitable. This is the Resolv Labs sub-class; TesseraDAO confirms it at small-cap scale on BNB Chain.

Public references

[peckshieldtesseradao2026] — PeckShield / on-chain analysis, 2026-06-01: TesseraDAO exploit minted ~99M TSR, ~$2.5M USDT realised, private-key leakage / ownership takeover; mint tx 2026-06-01 11:38:25 UTC. Via Bloomingbit, "PeckShield Says TesseraDAO Exploit Minted 99 Million TSR, Stole 2.5 Million USDT": https://en.bloomingbit.io/feed/news/113373
[usethebitcointesseradao2026] — UseTheBitcoin, "Hacker Drains $2.4 Million From TesseraDAO Through Unauthorized TSR Minting": https://usethebitcoin.com/news/tesseradao-hack-tsr-mint-exploit/
[cryptotimestesseradao2026] — Crypto Times, "TesseraDAO TSR Token Crashes 99% Following 99M Token Mint Exploit", 2026-06-02: https://www.cryptotimes.io/2026/06/02/tesseradao-tsr-plunges-99-after-attacker-mints-99m-tokens/
[chaincatchertesseradao2026] — ChainCatcher, "TesseraDao was attacked, hackers minted 99 million TSR and cashed out 2.5 million dollars" (notes bridge to Ethereum + ~1,285.5 ETH through Tornado Cash): https://www.chaincatcher.com/en/article/2268696
[cryptoeconomytesseradao2026] — Crypto Economy, "TesseraDAO Suffers $2.5 Million Exploit Following Ownership Takeover Attack": https://crypto-economy.com/tesseradao-suffers-2-5-million-exploit-following-ownership-takeover-attack/

Discussion

TesseraDAO is the small-cap BNB-Chain bookend of OAK's admin-key mint-and-dump series, joining Holograph (examples/2024-06-holograph.md), Resolv Labs (examples/2026-03-resolv-labs-usr-unlimited-mint-key-compromise.md), and Ankr aBNBc as worked examples of the same architectural defect. Its instructional value is precisely its unremarkable mechanics: there is no novel cryptography and no clever logic bug — just an unbounded mint behind a single key, exploited and laundered through the standard bridge-then-mixer tail. That ordinariness is the teaching point. The pattern recurs because the mitigation (circuit-breakers on retained mint authority) is a design discipline, not a detection capability, and small-cap projects repeatedly ship the mint surface without it. Contributors extending the mint-and-tokenomics cohort should treat TesseraDAO as confirmation that the Resolv "single key, no circuit-breakers" sub-class is chain- and scale-independent.