Someone Walked Into a Wallet, Signed With the Owner's Key, and Left With $19K in Aave Positions — and the Destination Is a Receive-Only Black Hole

On November 8, 2026, two long-held Aave positions worth about $19,254 were moved out of a single wallet with plain ERC-20 transfer() calls mined in the same block and sent to a receive-only EOA that has taken from hundreds of senders across dozens of tokens. Because plain transfer() requires the wallet's own key, this reads as key or session compromise rather than an approval drain, so revoking approvals would not have helped; the fixes are rotating to a fresh wallet, killing any transfer-capable session keys, preserving chain evidence, and watching whether the swept tokens ever reach a labeled exchange.

· Updated November 19, 2026 · Zain Tran · 8 min read · 3 total views · 3 today

Categories: technologyEthereumDeFi

Futuristic editorial illustration of a plain ERC-20 transfer sweeping two Aave staking positions out of a victim wallet into a receive-only drainer address

I have watched enough exploit threads to know what the scary part isn't. The scary part isn't the speed. It's that the transactions in this one are boring.

On November 8, 2026 at 18:10:35 UTC, two positions in one Aave user's wallet were moved out with plain, ordinary transfer() calls — selector 0xa9059cbb, the most vanilla function signature on Ethereum — mined in the same block. No exploit contract. No flash loan. No clever callback. Just the wallet's own key signing its own money away to an address that has never signed a single outbound transaction in its life.

That is the whole story in one sentence: a plain transfer() from your own wallet means your private key signed it. There is no approval to revoke afterwards, no permit to tear up, no admin key to blame. The key was in someone else's hands, and the chain did exactly what it was told.

Key Metrics at a Glance

Metric Value
Incident time 2026-11-08 18:10:35 UTC (both txs, same block)
Victim wallet 0x64cacba2bca8785961c450b928dc60b03742b3cc
Drainer address 0x413e4f4de7e5ff010913488f781e679e76f706da (EOA, nonce 0)
Token 1 taken AUSDT (aToken 0x23878914…4086a): 10,028.528651 ≈ $10,015.77
Token 2 taken stkwaEthUSDC.v1 (Umbrella 0x6bf18324…8aa6): 8,398.570816 ≈ $9,238.43
Total stolen ≈ $19,254 USD
Tx method plain transfer() (0xa9059cbb), 2 txs: 0x5223f78b…8fd44, 0x254c9313…93b4
Drainer profile receive-only: 1,810 inbound txs, 644 token transfers, 0 outbound, 326 senders, 91 tokens, active since 2026-11-07 17:50 UTC
Positions held since 2026-06-26 (untouched ~4.5 months before the sweep)
Public disclosure Aave governance forum, Nov 11, 2026 (topic 26207)

What Got Taken, and How Boring the Theft Was

The victim held both positions since June 26, 2026 — long enough that the wallet had become, in practice, a savings account. Long-held, low-activity wallets are exactly what sweeper bots love: they're not watched, and nobody is sitting on the "revoke" button when the key leaks.

The two theft transactions went to the same drainer in the same block, 18:10:35 UTC. After the sweep, the wallet's AUSDT balance read 0.001219 (dust) and the stkwaEthUSDC.v1 balance read exactly 0. Nothing has come back. There is no inbound transaction restoring either token.

Two more transactions in the thread deserve a hard look because they are NOT the thief's: the victim's indexer initially mis-attributed two transfers (0xdcc81d17…97a at 18:17:47 and 0x4157f599…35d at 18:17:59) to the victim wallet, but a direct chain read showed the on-chain from addresses were 0x1584a8ee…3c7dd and 0xd6434d15…6908 — neither is the victim. They went to a different address, 0x413e1868…06da. The amount in the first of those exactly equals the stolen AUSDT balance, which nobody can yet explain. If you're tracking this case, that coincidence is a lead, not a footnote.

Futuristic editorial illustration of a plain ERC-20 transfer() call moving two Aave staking positions out of a victim wallet in a single block

The Drainer's Signature: an Address That Only Receives

Here is what the destination address looks like on-chain, because the profile is the tell:

Trait Observation Why it matters
Account type EOA (eth_getCode empty) Not a contract — no code to audit, no admin to negotiate with
Nonce 0 Has never signed anything itself
Direction 0 outbound token transfers as of 2026-11-11 Pure sink; it accumulates and does not move
Inbound volume 1,810 transactions, 644 token transfers Industrial scale
Senders 326 distinct addresses Many victims, not one
Tokens swept 91 distinct (USDC, WETH, USDT, INJ, stETH, eETH, AAVE, ENA, PENDLE, ONDO, LINK, DAI, UNI + 78 more) Generic sweeper, not Aave-specific
First activity 2026-11-07 17:50 UTC Was already sweeping other wallets before this victim

A receive-only EOA with nonce 0 is not a hacker testing exploits. It's a dead-drop. Someone else is watching it, consolidating from elsewhere, and the address itself is just the mail slot.

Where the Key Actually Failed

The governance post says it plainly: "We did not sign these transactions, and we were not at the device at the time." But transfer() from your own wallet cannot be authorized by an approval — approvals authorize other addresses to move your tokens. A plain transfer() out of your own balance can only be signed by your key. So one of these is true:

  1. The private key or seed was exfiltrated (malware, clipboard hijack, fake site, poisoned update).
  2. A session key, agent, or automation with transfer rights was compromised.
  3. The device itself was compromised at signing time.

What this was NOT: an infinite-approval phishing drain (that uses transferFrom), and not a smart-contract exploit. The absence of transferFrom is actually good news in one narrow sense — revoking approvals right now would not have helped, because there was no approval involved. The bad news: there is nothing to revoke. If the key is compromised, the only real fix is moving everything to a fresh key — and doing it before the sweeper's next pass.

Key Exposure Score (proprietary framework)

KES = (Signing-surface isolation × 0.35) + (Activity monitoring × 0.25) + (Approval hygiene × 0.20) + (Key rotation readiness × 0.20)

Factor Weight This victim's reading
Signing-surface isolation (hot vs cold separation) 0.35 Weak — staking positions sat in the same wallet that was used for signing (0.2)
Activity monitoring (alerts on outbound txs) 0.25 Weak — positions untouched since June, no alerts mentioned (0.3)
Approval hygiene (no infinite approvals) 0.20 Irrelevant here — plain transfer(), not transferFrom (0.5)
Key rotation readiness (fresh key ready, funds movable fast) 0.20 Unknown at incident time (0.4)

KES ≈ 0.33 (≈3.3/10). The lesson isn't "be more careful with approvals." It's that the wallet holding your staked, yield-bearing positions should not be the wallet your browser can sign with.

Editorial visualization of the receive-only drainer EOA: thousands of inbound transfers from dozens of victims across 91 tokens, zero outbound

Decision Framework

You see outbound transfers from your wallet that you did not sign:
├── Was the method transferFrom (0x23b872de)?
│   ├── YES → an approval was abused: revoke ALL approvals now (revoke.cash / Etherscan Token Approvals),
│   │        then move remaining funds to a fresh wallet
│   └── NO (plain transfer, 0xa9059cbb) → YOUR KEY signed it:
│       ├── Assume key compromise: generate a NEW wallet offline, move everything there immediately
│       ├── Do NOT just "revoke approvals" — there is nothing to revoke
│       ├── Check for session keys / agents / automation with transfer rights and kill them
│       └── Preserve evidence: tx hashes, addresses, timestamps, indexer data (file a report)
├── Is the destination a receive-only EOA (nonce 0, inbound-only)?
│   └── YES → industrial sweeper dead-drop: funds are likely already consolidated; report to
│            the chain's forensic teams + exchanges (they watch these sinks), and post publicly
│            so other victims surface (as this Aave user did)
└── Any transactions your indexer attributes to you that don't match your chain read?
    └── Verify with a direct chain read (from field) before acting — indexers mis-attribute

Editorial visualization of the incident-response decision flow: transferFrom means revoke all approvals, plain transfer means rotate to a fresh key immediately, and a receive-only drainer means preserve evidence and report to forensics and exchanges

What To Watch

Watch item Why it matters
The unexplained second address 0x413e1868…06da Received a transfer whose amount exactly equals the stolen AUSDT, from wallets that aren't the victim's — could be a consolidation hop or a second campaign
Whether any of the 91 swept tokens reach a labeled exchange deposit That's the off-ramp; Chainalysis-style tracing + exchange compliance is the only realistic recovery path
Aave/Umbrella disclosure of root cause The forum post asks the community for guidance; an official postmortem on how the key leaked would help every user
Sweeper infrastructure rotating to new sink addresses Receive-only EOAs get flagged; expect new dead-drops (nonce 0, inbound-only) to appear
Wallet/session-key UX If the cause is a compromised automation session rather than the seed, wallet vendors need to make session-key scopes revoke-by-default

TL;DR

  • What: On 2026-11-08 18:10:35 UTC, ~$19,254 in Aave positions (10,028.53 AUSDT + 8,398.57 stkwaEthUSDC.v1) were transferred out of wallet 0x64cacba2…b3cc via two plain transfer() calls to drainer 0x413e4f4d…706da
  • Why it matters: plain transfer() means the victim's own key signed — this was key/session compromise, not an approval phishing drain, so revoking approvals would not have helped
  • The drainer: a receive-only EOA (nonce 0, zero outbound) that has taken from 326 senders across 91 tokens since 2026-11-07 — an industrial dead-drop, not a one-off hacker
  • Edge: two later txs mis-attributed by the victim's indexer went to a different address 0x413e1868…06da with an amount exactly matching the stolen AUSDT — unexplained, and a live lead
  • Watch: recovery depends on whether any swept tokens hit a labeled exchange; fresh wallet + key rotation is the only real fix; Aave community guidance requested in the Nov 11 forum post

Sources


Zain Tran is TotesTek's Ethereum Ecosystem Columnist & Accountability Reporter at TotesTek.