BlockSec reports a $24,200 loss due to a vulnerability in the MT token on the BSC chain.

iconChaincatcher
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
BlockSec reported a $24,200 loss on the BSC chain after on-chain data revealed a suspicious transaction targeting the MT-WBNB liquidity pool. On-chain analysis showed the exploit leveraged a flaw in the buy-limit mechanism, allowing attackers to bypass restrictions via routers and liquidity withdrawal. The attackers manipulated token prices and converted MT back to WBNB to profit.

ChainCatcher report: According to BlockSec monitoring, its system detected a suspicious transaction targeting the MT-WBNB pool on BSC, with an estimated loss of approximately $242,000. The vulnerability stemmed from a flaw in the buy restriction mechanism: under deflationary mode, normal buy transactions were reverted, but routers and trading pairs were whitelisted, allowing attackers to bypass restrictions by swapping via routers and removing liquidity to extract MT from the pair. The attacker then sold MT to accumulate pendingBurnAmount and called distributeFees() to directly burn MT from the trading pair, artificially inflating the price, before swapping the MT back to WBNB for profit. Additionally, a referral rule permitting the first 0.2 MT transfer to bypass buyer restrictions enabled the attacker to initiate the attack.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.