ChainBleedv0.1 · open intel
← back to feed·ETHPHISHING2026-04-28 · 1mo ago
Incident · TENARMOR

Multicall yvETH Approval Abuse (victim 0x9828)

Approval-drainer via multicall aggregator (phishing pattern)
Estimated loss
$980.1K
VERDICT —OUT OF SCOPE
Root cause is phishing — victims signed malicious transactions or approvals off-protocol. Contract logic was not the failure surface; user-side wallet hygiene was. Pre-deployment audit cannot catch this class.
▰ METHOD
Approval-drainer via multicall aggregator (phishing pattern)
PHISHING
Root cause

Victim 0x9828 had previously granted ERC20 approval over their yvETH (Yearn Vault ETH) balance to contract 0x143a, which TenArmor identified as a 'multicall aggregator'. The attacker invoked the aggregator to chain calls through it, ultimately executing transferFrom against the victim's approval to drain ~$980K of yvETH. The vulnerability is NOT a smart-contract bug in yvETH or in the aggregator per se — it is the classic stale-approval / malicious-aggregator drain that defines modern crypto phishing: a victim grants over-broad approval (often max-uint256) to a contract they trusted at signing time, and the contract's operator later weaponizes it. Mitigation is approval hygiene (revoke after use, prefer permit2-style time-limited approvals, use approval-tracking tools like Revoke.cash) — not a smart-contract patch.

Forensic narrative

Method: Approval-drainer via multicall aggregator (phishing pattern). Root cause: Victim 0x9828 had previously granted ERC20 approval over their yvETH (Yearn Vault ETH) balance to contract 0x143a, which TenArmor identified as a 'multicall aggregator'. The attacker invoked the aggregator to chain calls through it, ultimately executing transferFrom against the victim's approval to drain ~$980K of yvETH. The vulnerability is NOT a smart-contract bug in yvETH or in the aggregator per se — it is the classic stale-approval / malicious-aggregator drain that defines modern crypto phishing: a victim grants over-broad approval (often max-uint256) to a contract they trusted at signing time, and the contract's operator later weaponizes it. Mitigation is approval hygiene (revoke after use, prefer permit2-style time-limited approvals, use approval-tracking tools like Revoke.cash) — not a smart-contract patch. Notes: Attacker contract: 0x143a (multicall aggregator). Approval-drainer pattern. Attack tx: 0xebaaab69baa3cd2543eb80ecfb8e3ed226b9e5a6f5694891a8adf4edbcbd8107. First flagged by TenArmor TenMonitor.

Primary source
https://etherscan.io/tx/0xebaaab69baa3cd2543eb80ecfb8e3ed226b9e5a6f5694891a8adf4edbcbd8107
Sourced from
tenarmor
Technical record
chain
ethereum
protocol
Multicall yvETH Approval Abuse (victim 0x9828)
bug_class
phishing
date_occurred
2026-04-28
loss_usd
$980,100
source_id
tenarmor:ethereum:0xebaaab69baa3cd2543eb80ecfb8e3ed226b9e5a6f5694891a8adf4edbcbd8107
Related — same bug class· phishing
2026-04-29
1mo ago
Sweat Foundation
Contract Vulnerability
phishing
$3.50M
OUT OF SCOPE
2026-04-27
1mo ago
ETH
Unverified Contract 0x2990A16D
Stale approval drain on unverified contract
phishing
$229.0K
OUT OF SCOPE
2026-04-03
2mo ago
Adobe
Supply Chain Attack
phishing
OUT OF SCOPE
2026-04-02
2mo ago
Trust Wallet
Infrastructure Hijacking
phishing
OUT OF SCOPE
2025-12-04
6mo ago
USPD
"CPIMP" (Clandestine Proxy In the Middle of Proxy) attack
phishing
$1.00M
OUT OF SCOPE
2025-11-11
7mo ago
Polymarket
Phishing attack
phishing
$500.0K
OUT OF SCOPE
ChainBleed — live web3 threat intelligence