IoTeX (IOTX)

#PeckShieldAlert In Feb. 2026, the crypto space saw 15 main hacks totaling $26.5M, representing a 98.2% YoY decrease compared to Feb. 2025 ($1.5B, including the $1.4B #Bybit drain) and a notable 69.2% MoM decrease from Jan. 2026 ($86.01M in losses). #Top5 Hacks : YieldBlox[.]finance: $10M IoTeX[.]io Bridge (@iotex_io): $8.8M @crosscurvefi: $3M @FOOMCASH: $2.26M Moonwell: $1.8M

#IoTeX was hit by a private key exploit a week ago that drained ~$2M from bridge contracts and in the last 24 hours or so it's surged ~508%. What are y'all doing with $IOTX? https://t.co/beMlGUJH3P

IoTeX ($IOTX) deposits and withdrawals are now live again on @binance. Network is running at full capacity. All systems operational. Exchange partners are resuming services as scheduled. This is what rapid recovery looks like. 🦾🪖 https://t.co/UQJSAPQdDZ

We will host a livestream this Friday @ 12pm PT in the IoTeX Discord (https://t.co/lyQb7qiFqp) with the core team to update our community on the ioTube bridge attack and demo our Claims Portal, which will go live tomorrow to fully compensate impacted users. More details below 👇

⚠️ IoTeX activates plan after attack IoTeX announces recovery strategy after the hack and confirms that it will compensate 100% of affected users. 📰 Full article: https://t.co/fu1A3whQu2

IoTeX released the third progress update and compensation plan for the ioTube cross-chain bridge security incident, stating that it has completed 100% tracking of the on-chain flow of stolen funds and continues to cooperate with exchanges, security agencies, and law enforcement; it also promises that regardless of the final recovery outcome, the IoTeX Foundation will provide 100% compensation to eligible affected users. The plan shows that affected users will be compensated in tiers based on the amount: users with $10,000 or less will receive a one-time full compensation once the claim portal is launched; amounts exceeding $10,000 will be disbursed quarterly over 12 months, with an additional 10% compensation in the form of IOTX locked for 12 months. https://t.co/lVIuMCLCpk

📢 Exchange Service Recovery Update IoTeX mainnet has been fully operational since February 24. Exchange services are progressively resuming: ✅ Full service (deposits + withdrawals): @coinbase @MEXC_Official ✅ Withdrawals LIVE: @binance @Official_Upbit 🔄 Resuming soon: @bitget @gate_io @wallet @BithumbOfficial @kucoincom @HashKey_Global @BitMartExchange and others We are in direct contact with all exchange partners to restore full services as soon as possible. Updates will follow as each exchange comes online. We are also working closely with law enforcement agencies, leading blockchain analytics firms, and asset recovery specialists to trace and recover the stolen funds. The attacker's movements are being monitored in real time. Thank you to our exchange partners and community for the continued support. 🙏

after hack 4 - IoTex Private Key Compromise @0xswapnet @claudeai Hack occurred on 26.01.26 An incident on Jan 1, 26 where 13M was stolen after approval. Due to a vulnerability in the swapnet contract, the hacker siphoned funds from victim wallets that had approved swapnet. BASE -> Relay Bridge -> Ethereum Total loss $13.34M Ethereum addresses currently holding assets 0x6cAad74121bF602e71386505A4687f310e0D833e 0x8bcd90f63e998e7c2cda4b5dea8cb7fe8ca5ea81 0x7402875231D63FE9e30D854c526910581386E5D2 0x21fbC7050F3bd934D9963655724C34205cbdf100 0x578D892aC5A25CA46E03b9A5C4C2C2679894C400 0x6A715e758bE14502F6aaF0643594e99dF93ab1f7 0x61d7cC832F967e78Ba2D167358899Ec11622193b 0xd640b6e0a4da928a1fb46de9b8fec695e14c284a ======= During development, it seems intra-chain transfers are generally not problematic, but swap processing and the bridge part have the most issues. Thorswap appears to have the most problems among bridges, Relay is fast and convenient, so it is used a lot, though it has some complexities.

after hack3 - IoTex Private Key Compromise @claudeai @iotex_io I tracked the recent IoTex validator key leak incident. I transferred assets to ETH and swapped to BTC using Thorswap. While tracking Thorswap transactions, various issues arose, taking a long time to plot the timeline, and since it hasn't been fully fixed, I need to test a few more cases that route through Thorswap.