TransitFinance suffers $1.88M hack; stolen funds in DAI address 0x8a634DfA2609358849D7D65FFA270C8A57a8abA5, per PeckShieldAlert.

KelpDAO suffers $290M attack linked to North Korea, sparking crypto security concerns amid Bitcoin market volatility and DeFi hack trends.

Bank trades push Clarity Act markup to May amid intense lobbying, while a multi-million-dollar DeFi hack escalates crypto market vulnerabilities in 2026.

KelpDAO suffers $294M exploit as hacker mints 116,500 rsETH, dumps and borrows 106,467 ETH ETH, sparking crypto market crash fears.

According to @PeckShieldAlert, Unleash Protocol on Story Protocol suffered an unauthorized drain with an estimated ~$3.9 million loss, after which the exploiter bridged the proceeds to Ethereum and deposited 1,337.1 ETH into Tornado Cash (source: @PeckShieldAlert). According to the official incident notice from Unleash Protocol, an externally owned address obtained administrative control via Unleash’s multisig governance and executed an unauthorized contract upgrade that enabled unapproved asset withdrawals; impacted assets identified so far include WIP, USDC, WETH, stIP, and vIP, and all Unleash operations have been paused while the investigation proceeds (source: Unleash Protocol official incident notice on X). Unleash also stated there is no evidence that Story Protocol contracts, validators, or underlying infrastructure were compromised, and the impact appears limited to Unleash-specific contracts and administrative controls (source: Unleash Protocol official incident notice on X). For trading risk management, Unleash advised users to refrain from interacting with Unleash Protocol contracts until further notice and noted they are evaluating remediation and recovery measures, with on-chain data preservation and coordination underway (source: Unleash Protocol official incident notice on X). The on-chain route of 1,337.1 ETH to Tornado Cash indicates obfuscation of flows tied to the exploit, as flagged in real time (source: @PeckShieldAlert).

According to @PeckShieldAlert on Dec 17, 2025, YearnFinanceV1 suffered an exploit with an estimated total loss of about $300,000. According to @PeckShieldAlert, the exploiter swapped the stolen funds into 103 ETH now held at address 0x0F21...4066. According to @PeckShieldAlert, the alert identifies the impacted environment as YearnFinance V1 and does not detail the attack vector.

According to @PeckShieldAlert, Yearn Finance suffered an exploit with an estimated total loss of approximately 300,000 dollars. According to @PeckShieldAlert, the attacker converted the stolen funds into 103 ETH and currently holds the funds at address 0x0F21...4066. According to @PeckShieldAlert, traders should monitor outbound movements from 0x0F21...4066 for potential transfers to exchanges or mixers as an immediate on-chain risk signal. According to @PeckShieldAlert, the alert did not include remediation details or a recovery plan from Yearn Finance.

According to @PeckShieldAlert, a Goldfinch user wallet (deltatiger.eth) was attacked with an estimated loss of about $330,000, and the attacker deposited 118 ETH of the stolen funds into Tornado Cash, source: @PeckShieldAlert on X, Dec 2, 2025. According to @PeckShieldAlert, users are urged to revoke approvals for the specified contract immediately, source: @PeckShieldAlert on X, Dec 2, 2025.

According to @PeckShieldAlert, Yearn Finance suffered an approximately $9 million exploit where an attacker minted a near-infinite amount of yETH and drained the pool in a single transaction, and about 1,000 ETH (around $3 million) was sent to Tornado Cash (source: @PeckShieldAlert on X, Dec 1, 2025). For trading, monitor YFI spot and perpetual markets, yETH-linked liquidity, and on-chain flows related to the 1,000 ETH mixer outflow flagged in the report for signs of liquidity stress or volatility (source: @PeckShieldAlert on X, Dec 1, 2025). Consider tightening risk on DeFi exposure and setting alerts for additional transfers from the exploiter wallet given the confirmed pool depletion and Tornado Cash routing described in the alert (source: @PeckShieldAlert on X, Dec 1, 2025).