Curriculum·J311 Privacy, Surveillance, and Compliance Exposure·about 33 min
Defensive hygiene
By the end of this lesson you can
- →Explain why a public ledger enables targeting in real time rather than only retrospectively
- →Compute what an attacker can and cannot afford to match in an address, and verify accordingly
- →Assemble the separation policy that bounds what any single failure reaches
- →Price the hygiene against the exposure it removes
Junior · enrolled learners
This lesson opens with The WBTC address poisoning, 3 May 2024.
- What happened
- A holder moving 1,155 WBTC, about $68M, created a fresh destination address. An attacker watching their on-chain activity generated an address whose leading and trailing characters matched that destination, then sent a token transfer from it so that the lookalike appeared in the holder's transaction history. The holder copied the address from that history and sent the full amount to the attacker. The attacker converted the proceeds to ether. Negotiations conducted through Match Systems and Cryptex began around 10 May and the attacker returned approximately 22,960.07 ETH, roughly $65.7M and more than 96 percent of the dollar value taken.
- The decision point
- No key was compromised, no contract was exploited and no approval was abused. The attack required only that the target's activity was readable while it was happening, which per J311-01 is a property of the ledger rather than a mistake anybody made. The single defeating check was comparing characters an attacker could not afford to match, and the single enabling habit was copying an address from a history that anybody can write to.
- Recorded loss
- $68,000,000
What you will be able to answer
- →Why is public activity a live risk rather than a historical one?
- →What can an attacker afford to match?
- →So what do you verify?
- →What is the separation policy?
Orientation and Year One are open: anyone can read them without an account. From Year Two onward the lessons are for enrolled learners, because progress through the later years only means anything if it is tracked against a record.
It is free. We do not sell the list and there is nothing to buy at the end of it.
Sources and review
- https://www.theblock.co/post/293908/victim-of-71-million-address-poisoning-attack-recovers-funds-following-negotiations
- https://unchainedcrypto.com/68-million-stolen-in-dust-attack-returned-to-victim/
- https://www.chainalysis.com/blog/address-poisoning-scam/
- https://www.theblock.co/post/292472/victim-loses-over-71-million-worth-of-wbtc-in-purported-address-poisoning-attack
Confidence high·Volatility low·Reviewed 2026-08-06·Owner unassigned
Contested
Reported figures for this incident range from about $68M to $72.6M depending on the WBTC price used and the moment of valuation, and the returned amount is reported at roughly $65.7M. The recovery came from negotiation with the attacker rather than from any mechanism, and per J301-05 it must not be treated as a base rate for anything.
The generation-rate figure in part two, being roughly five million candidate addresses per second, is an order-of-magnitude assumption for ordinary hardware, stated so the arithmetic can be checked and re-derived. The conclusion, which is that matching eight characters is cheap and matching twelve is not, holds across a wide range of plausible rates.
F106-03 owns personal opsec, being credentials, devices and recovery chains. This lesson owns the hygiene that follows from a public ledger specifically, being address separation, verification and the disclosed surface. Keep the split.