CertiK flags $820K exploit draining NEM token’s PancakeSwap liquidity pool
Published Updated 1 new report since it was first published
Security alerts identified an exploit affecting NEM’s PancakeSwap USDT/NEM liquidity pool, with both coverage items putting the drain at about $820,000. One report also points to the NemTokenV2 contract’s sell-tracking logic as the apparent path used to manipulate pool reserves.
What this rests on
What it means
NEM is a token with liquidity on PancakeSwap, the Binance Smart Chain-based decentralized exchange where token pairs are traded through pools rather than a traditional order book. A security alert from 0xCERT placed the incident in the USDT/NEM pool, and CertiK also identified the episode as a PancakeSwap liquidity exploit. The fact that both alerts focus on the pool rather than a broader platform outage points readers to a contract-level problem in how that market was functioning.
For users and builders around NEM, the immediate practical issue is that liquidity in the USDT/NEM pool was drained and the pool’s reserves were left altered. Anyone relying on that pair for swapping or price discovery would need to treat the market structure as compromised until the contract and pool are reviewed. DeFi projects that design tokenomics around automated liquidity now face the same basic question: whether the contract logic is robust enough to withstand manipulation.
The larger tension is between permissionless token markets and the risk that contract logic can be used against the pool itself. PancakeSwap is built for open access, but open access also means flaws in token contracts can become an on-chain route into shared liquidity. This case sits in the uncomfortable space where decentralized trading is still only as safe as the code behind each pair.
Still open is whether the sell-tracking logic identified in the alert is the full explanation for how the pool was drained and whether any recovery steps will follow. The record here does not say who was behind the exploit or whether funds were recovered. A contract review, a postmortem from the NEM team, or an updated alert from security firms would settle those points.
Market reaction
How the story was built
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 5 months ago | Echo Bridge · Private Key Compromised incident | $821k |
| 4 months ago | Hinkal incident | $820k |
| 3.4 years ago | Pawnfi incident | $820k |
| 3.5 years ago | MetaPoint · Token Approval Abuse incident | $820k |
| 4.6 years ago | ApeCoin · Flashloan governance attack incident | $820k |
4221 incidents stored · 986 were as large as this one or larger ($820k)