A PancakeSwap liquidity pool tied to the 79AU token has been drained of $14.35 million in USDT, even though the project had locked its liquidity before the incident — a safeguard many investors treat as a baseline signal that a token is legitimate.

What Happened to the 79AU Pool

PancakeSwap is a decentralized exchange, meaning trades are executed automatically through smart contracts — self-running programs deployed on a blockchain — rather than through a centralized intermediary. The exchange operates on BNB Chain, the blockchain network associated with the Binance ecosystem. Tokens like 79AU rely on liquidity pools, which are shared reserves of funds that allow buyers and sellers to trade against one another.

According to CryptoSlate's reporting, the 79AU pool on PancakeSwap lost $14.35 million worth of USDT. USDT, issued by Tether, is the largest stablecoin by market capitalization and is pegged to the US dollar, meaning each token is designed to hold a value of $1.00. Stablecoins have become central infrastructure for DeFi pools, and their role in payments is expanding as companies add stablecoin payment rails to enterprise platforms.

Before the incident, the 79AU project had put a liquidity lock in place. In practice, such a lock typically means a pool's LP tokens are held in a time-locked contract that the team cannot access until a predetermined date. Liquidity locks are frequently promoted as a sign of trustworthiness because they stop a team from pulling its own funds out of the pool and disappearing — a type of scam known as a “rug pull.”

Why Locked Liquidity Did Not Stop the Drain

A liquidity lock does one specific thing: it prevents the token team from withdrawing the liquidity it deposited, typically for a set period of time. It does not make the smart contract itself secure. In other words, the lock protects the team's deposit — not the integrity of the code governing the pool.

Smart contracts can contain vulnerabilities in their code. They can also be written with special permissions — sometimes called admin keys or owner functions — that allow certain addresses to mint new tokens, change fees, or otherwise interact with a pool in unexpected ways. A lock on the team's own LP (liquidity provider) tokens does nothing to block those interactions.

As CryptoSlate noted, the 79AU incident illustrates precisely how a locked-liquidity label can create a false sense of safety. The lock addresses one narrow risk while leaving contract-level risks untouched.

An analogy makes the gap clear: locking the front door of a house proves the owner cannot leave through the front, but it says nothing about whether the windows are open or whether someone already has a copy of the key.

What the Incident Means for DeFi Users

For anyone holding tokens or considering a DeFi investment, the 79AU drain is a reminder that a single safety signal is rarely enough. A liquidity lock is one checkbox, not the whole checklist. Before putting money into any token project, the following checks are worth considering:

• Smart contract audit: Has an independent security firm reviewed the contract code? An audit does not guarantee safety, but it reduces the risk of obvious vulnerabilities.
• Mint and ownership permissions: On Bsc, the block explorer for BNB Chain, where PancakeSwap operates, users can check whether the contract owner still holds special privileges that could affect the pool.
• Pool depth and concentration: A pool in which a small number of wallets hold most of the liquidity is more vulnerable to sudden, large-scale movements.
• Official updates: After an incident like this, users should check a project's verified social channels before making any decisions about buying, selling, or holding.

Security threats across crypto continue to evolve. Europol has warned that upgrading crypto wallets to resist emerging threats could take years, underscoring that on-chain due diligence matters more than surface-level signals like a liquidity lock.

For newcomers, the practical rule is straightforward: a liquidity lock tells you the team cannot easily execute a rug pull, but it tells you nothing about whether the contract is safe, whether the code has been audited, or whether the project can withstand an exploit. No single check above is sufficient on its own; together they form a more reliable picture of a project's risk profile. Locked liquidity should be treated as a minimum bar, not a seal of approval.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always verify information through official sources and do your own research before making decisions.