📢 Exclusive on Gate Square — #PROVE Creative Contest# is Now Live!
CandyDrop × Succinct (PROVE) — Trade to share 200,000 PROVE 👉 https://www.gate.com/announcements/article/46469
Futures Lucky Draw Challenge: Guaranteed 1 PROVE Airdrop per User 👉 https://www.gate.com/announcements/article/46491
🎁 Endless creativity · Rewards keep coming — Post to share 300 PROVE!
📅 Event PeriodAugust 12, 2025, 04:00 – August 17, 2025, 16:00 UTC
📌 How to Participate
1.Publish original content on Gate Square related to PROVE or the above activities (minimum 100 words; any format: analysis, tutorial, creativ
The Poolz project was attacked, resulting in a loss of $665,000 across multiple chains.
Poolz project suffers an attack, resulting in a loss of approximately $665,000
Recently, a security incident involving multiple blockchains has drawn industry attention. According to on-chain monitoring data, on the early morning of March 15, the Poolz project on the Ethereum, Binance, and Polygon networks was attacked, resulting in a significant loss of tokens, with a total value of approximately $665,000.
The attacker exploited an arithmetic overflow vulnerability in the smart contract and successfully extracted multiple tokens from the project, including MEE, ESNC, DON, ASW, KMON, POOLZ, etc. Currently, some of the stolen tokens have been exchanged for BNB, but the funds have not yet been transferred.
The recent attack primarily targeted the CreateMassPools function of the Poolz project. This function was originally designed to batch create liquidity pools and provide initial liquidity. However, due to an integer overflow issue in the getArraySum function, the attacker was able to exploit this vulnerability. By passing in specific parameters, the accumulated result exceeded the range of uint256, causing the function to return a value of 1. This allowed the attacker to record a liquidity amount in the system that was far greater than the actual quantity by only transferring 1 token.
Subsequently, the attacker called the withdraw function to extract the tokens, completing the entire attack process.
To prevent similar incidents from happening again, industry experts recommend that developers use newer versions of Solidity for compilation, as these versions automatically perform overflow checks. For projects using lower versions of Solidity, it is advisable to consider incorporating OpenZeppelin's SafeMath library to address integer overflow issues.
This incident reminds us once again that security is crucial in smart contract development. Developers need to pay extra attention to potential arithmetic overflow risks and take necessary precautions. At the same time, conducting regular security audits is also an important means of ensuring project safety.