Coin Alerts

TOP news archive

3 stories

Last checked

Refresh

Estimated news impact scores by coin. Scores are not price-change percentages.

Newest first

Check failed. Showing saved news from .

  1. Published Social post

    GoPlus Security 🚦 (@GoPlusSecurity)

    🧵1/3 🧯Old contract exploits keep happening — how should projects respond? Recently, smart contract vulnerability attacks have been occurring frequently. In particular, legacy contracts deployed years ago are being increasingly exploited as attackers leverage AI techniques to surface vulnerabilities, causing significant losses for both projects and users. ▪︎ On June 9, the Token of Power (TOP) contract on #ETH, deployed 7 years ago, was exploited, resulting in a loss of approximately $1.5 million; ▪︎ On May 25, the 3-year-old contract of http://WUSD.fi was attacked, causing a loss of around $200,000; ▪︎ On June 14 and June 18, @aztecnetwork was attacked twice consecutively, both due to a 2-year-old legacy contract being exploited, with total losses exceeding $4 million. To address this crisis, adopting AI-based continuous and always-on audit services may be the only effective path forward. AI audits can complete security checks on historical contracts in a short time, balancing reliability and cost-effectiveness, helping eliminate these hidden risks for projects and developers. GoPlus’ AI continuous audit platform DeepScan reviewed several recent legacy contract exploit incidents and found that DeepScan could detect the vulnerabilities within a very short time. Losses that could have been prevented were instead handed over to attackers — a truly unfortunate outcome. 👉12 minutes to detect the Token of Power (TOP) contract vulnerability

  2. Published Social post

    GoPlus Security 🚦 (@GoPlusSecurity)

    🧵1/4 ⚠️ Vulnerability Analysis: Token of Power Exploit Analysis Token of Power (TOP) on #TH was exploited due to a #AragonDAO misconfiguration, resulting in a loss of 944.2 $WETH, approximately $1.5 million. Attack Mechanism Analysis: 1. The attacker completed the entire process of submitting, voting on, and executing an execution script within the same transaction. During this process, there was no timelock between script submission and voting, nor between voting and execution. Whether the vote could pass was determined by the ratio between a user’s $TOP balance and the total supply. The attacker held 8,192.000001 TOP, while the total supply was 16,384, meaning the attacker held more than 50% of the total $TOP supply. As a result, the attacker was able to pass the voting threshold alone and execute the proposal within a single transaction.

Showing 3 of 3 stories. Filters apply to the full news archive.