CCC, a token on BNB Smart Chain, was hit by an exploit on Aug. 28 that blockchain security firm TenArmorAlert said caused an estimated $117,000 in losses. The alert tied the incident to abuse of the token contract’s sell() function rather than a straightforward drain of assets from a liquidity pool.
According to TenArmorAlert, the attacker used the function to burn CCC tokens held by the project’s liquidity provider pair. The firm said that action was followed by abnormal price movement, but it had not released a full technical reconstruction of the exploit at the time of its notice.
Security alert points to LP pair token burn
TenArmorAlert said its monitoring system detected suspicious activity involving CCC on BSC and traced the event to the contract’s sell() function. In the firm’s description, the function was used to burn CCC directly from the liquidity pool pair, changing the token balance inside the pair rather than removing funds through a typical pool withdrawal.
The firm identified an attack transaction beginning with 0x89d805064. It estimated the loss at roughly $117,000, though it did not publish a complete accounting of the assets taken or the attacker’s final proceeds.
Price disruption followed the contract interaction
The reported exploit appears to have centered on tokens held inside the LP pair. Burning part of a token balance from a trading pair can alter the reserves that underpin pricing in that pool, and TenArmorAlert linked the CCC incident to abnormal market movement after the burn occurred.
Even so, several key details remain unclear. The available information does not explain how the attacker gained the ability to trigger the affected function, whether any access controls were bypassed, or whether another contract interaction was needed before the burn could be executed.
Several operational details remain unconfirmed
At the time of the alert, no post-mortem had been published and no recovery plan had been announced. There was also no disclosed compensation proposal for affected parties, including liquidity providers.
TenArmorAlert named BSC as the affected network, but it did not identify the decentralized exchange where the liquidity pair was hosted. Independent reports cited the same estimated loss figure and the same explanation involving the sell() function.
What is known next
For now, the confirmed facts are limited to TenArmorAlert’s account: suspicious activity was detected on Aug. 28, the sell() function was reportedly used to burn CCC from the LP pair, and losses were estimated at about $117,000.
The next meaningful update would be a detailed technical analysis from the security firm or the CCC team, including the full attack sequence, any contract changes or emergency measures, and whether funds can be recovered or users compensated. Until then, the exact exploit path and its aftermath remain unresolved.
Source: crypto.news