Ethereum funds unlocked via exploit

1,003.62 ETH ($2M) locked for nine years in HongCoin ICO was recovered by white-hat researcher Florent via an integer overflow vulnerability.

avatar

$RENDER is looking prepared to test the key resistance of an Ascending Triangle on the 1D chart. 📈

A successful breakout and confirmation above this zone could open the door for a strong 70-80% bullish move in the mid-term. Volume is gradually building, and market structure remains constructive.

As long as support holds, bulls stay in control. Keep this one on your watchlist — a major move could be closer than many expect. ✍️ $CHZ

#Solana proposes token burn mechanism

#Ethereum funds unlocked via exploit

avatar

$MET is holding support really well and showing strong signs of accumulation. 📈

Momentum is gradually building, and if buyers continue to step in, a solid breakout move could be just around the corner.

The chart structure looks healthy, and a nice upside rally may develop from this zone.

Keeping it on the watchlist and watching closely for confirmation. 👀 $MET

#Ethereum funds unlocked via exploit

#Anthropic files IPO paperwork

avatar

Nearly all $220 million stolen from Kelp DAO has been laundered—on-chain tracking is rendered ineffective against THORChain, Wasabi, and Tornado Cash. This is no isolated case—Radiant Capital just shut down after a $50 million attack, and the Gnosis Pay vulnerability continues to unfold. The trust ledger of cross-chain bridges is being rewritten repeatedly. Hackers used THORChain to bridge $175 million in ETH to Bitcoin, then mixed and split the funds, pushing THORChain’s daily trading volume to $394 million. Privacy tools are nothing new, but this scale exposes a structural issue: the more vibrant cross-chain liquidity becomes, the more mature the money-laundering channels grow. The only $71 million in ETH that was frozen is now entangled in legal disputes—victims’ families from North Korea seek to seize it as compensation. Under court injunctions, whether this money can be recovered remains uncertain. DeFi’s security assumption is shifting from “code is law” to “law is the last line of defense.” For the market, this is not a story of “bad news priced in.” After each attack, protocols strengthen audits—but hackers evolve too. Rising costs of cross-chain trust will ultimately manifest in funding rates, TVL, and user behavior—would you place your assets on a network vulnerable to money-laundering pipelines? $btc #eth #defi #onchaindata #ai

avatar

Not all DeFi failures start with a hack. Firelight will cover both technical and economic failures, including bad debt and structural impairments across collateral and loan asset relationships. Every claim will be backed by clear triggers and verifiable on-chain evidence.

avatar

The bug bounty program has received a high volume of submissions since launch. To give each report the attention it deserves, we're pausing new submissions while we work through the queue. We'll share an update when the program reopens. Thanks to everyone who's engaged so far.

avatar

Hee. "Only those who can afford $1M in security measures may remain in the market." > Mythos scanning detected over 20 critical vulnerabilities in Palo Alto Networks’ proprietary source code, consuming over $1 million in tokens.

avatar

Whitehat recovery: researcher Florent coordinated with the HongCoin team to unlock ~1,003 ETH (~$2M) stuck in a 2016 ICO refund contract due to legacy overflow/refund-logic bugs. #Ethereum #SmartContractSecurity

avatar

Reentrancy Decoded - The Smart Contract Bug Still Draining Millions in 2026, and the Checks-Effects-Interactions Pattern That Stops It in Code Reentrancy is not magic. It is an ordering bug: your contract updates its own state AFTER it makes an external call instead of before, and an attacker calls back in during that gap. Fix the order and the bug is gone. The DAO lost about 3.6M ETH (roughly $60M, around 5% of all ETH then in existence) to this exact mistake on June 17, 2016. The fallout split Ethereum into ETH and ETC. Ten years on, it is still draining funds. Solv Protocol lost $2.73M to a reentrancy on March 5, 2026, and roughly $52M was stolen across onchain protocols in May 2026 (DeFiLlama via CryptoTimes, May 31, 2026). The vulnerable pattern: read the balance, send the ETH with a low-level call, THEN set the balance to zero. The attacker's receive() function re-enters withdraw() before that zero ever lands, and loops until the contract is empty. Two fixes, used together: Checks-Effects-Interactions. Validate, update ALL state, then make the external call LAST. Move balances[msg.sender] = 0 above the call and the re-entrant call reads zero and reverts. OpenZeppelin's nonReentrant guard. A storage mutex (NOT_ENTERED to ENTERED) that reverts on re-entry. Use it AND CEI, not one or the other. Two things most developers still get wrong. 1. .transfer() is no longer a shield: the 2300 gas stipend stopped being a safe assumption when EIP-1884 raised SLOAD gas in 2019. Use .call{value:}("") with CEI. 2. read-only reentrancy bypasses a standard guard, because a view function read mid-update returns corrupted state and can poison a price oracle (dForce, $3.64M). For educational purposes only. Not financial advice. Follow for daily insights - where blockchain meets AI, one satisfying swipe at a time. #Solidity #SmartContractSecurity #Web3Security #Ethereum #DeFi #SmartContracts #BlockchainDeveloper #SolidityDev #EVM #OpenZeppelin #Reentrancy #Web3Dev #BlockchainSecurity #DeFiSecurity #SmartContractAudit #CodeSecurity #OnChain #BlockchainEducation