Worked example · 2011-06

Allinvain first major Bitcoin theft — Bitcoin — 2011-06-13

Loss: approximately 25,000 BTC stolen from a single user's Windows PC. At the June 2011 Bitcoin price of approximately $15–$30/BTC, the loss equated to approximately $375,000–$750,000 at then-prevailing exchange rates. At Bitcoin's late-2017 peak (~$20,000/BTC), the notional value exceeded $500M. At Bitcoin's 2024 all-time highs, 25,000 BTC represents approximately $1.7B+ in notional terms — the earliest documented case of a single-user Bitcoin theft that would reach billion-dollar-equivalent notional value. The attacker(s) were never publicly identified.
Recovery: zero on-chain recovery. The stolen Bitcoin was not recovered, and no law-enforcement disposition was ever publicly disclosed.
OAK Techniques observed: OAK-T15.004 (Credential Compromise — the attacker stole the unencrypted wallet.dat file from the victim's Windows PC. The file contained the private keys controlling the 25,000 BTC. The specific compromise vector — malware, remote-access trojan, or direct filesystem access — was never publicly established, but the extraction mechanism (stolen wallet file containing private keys) is the canonical T15.004 credential-compromise pattern for the pre-HD-wallet era). OAK-T15.003 (Operator Endpoint/Infrastructure Compromise — broadly construed; the victim's Windows PC was the endpoint, and the compromise surface was the local filesystem storing an unencrypted wallet.dat). OAK-T11.005 (Operator-Side Fake-Platform Fraud — not directly applicable to the theft mechanism, but the Allinvain case established the victim-side paradigm that "your Bitcoin is only as secure as the computer your wallet.dat file lives on" — a lesson that directly informed the early Bitcoin community's understanding of custody risk and prefigured the T11 surface).
Attribution: unattributed The attacker(s) have never been publicly identified. The BitcoinTalk forum post by user "allinvain" (June 13, 2011) is the primary-source contemporaneous record. No law-enforcement agency has publicly named any individual or group in connection with the theft through the OAK v0.1 cutoff.
Key teaching point: The Allinvain theft of June 2011 is the earliest documented case of a single-user Bitcoin theft on the public record — the ur-incident that established that Bitcoin's cryptographic security model does not extend to the endpoint where private keys are stored. Before the Allinvain theft, the dominant Bitcoin community security narrative was that Bitcoin's cryptography made it "unhackable." After Allinvain — and the subsequent wave of wallet.dat-targeting malware and remote-access attacks that followed through 2011-2014 — the community learned that the key-storage endpoint, not the blockchain's cryptography, was the relevant security surface for individual holders. The incident is the foundational anchor for every subsequent endpoint-compromise-to-private-key-extraction attack class, from clipboard hijackers (2014+) to infostealer malware (2020+) to EDR-bypass credential-access techniques (2024+).

Summary

On June 13, 2011, a BitcoinTalk forum user operating under the handle "allinvain" posted a thread titled "I just got hacked — 25,000 BTC stolen" — the first publicly documented case of a single-user Bitcoin theft of meaningful magnitude. The user reported that approximately 25,000 Bitcoin — accumulated through early Bitcoin mining when mining difficulty was low and a single consumer GPU could mine hundreds of BTC per day — had been stolen from their Windows computer's wallet.dat file. The victim reported that the wallet.dat file was not encrypted (Bitcoin Core's wallet-encryption feature, encryptwallet, was not yet widely used by early miners in mid-2011).

The theft vector remains technically unconfirmed in the public record. The victim speculated in contemporaneous forum posts that the attacker may have gained access through a Windows remote-access vulnerability or through malware delivered via a compromised download. The BitcoinTalk thread became one of the most-viewed security-discussion threads in Bitcoin's early history, with community members (including early Bitcoin developers) analyzing blockchain transactions to trace the stolen funds. The attacker(s) moved the 25,000 BTC through multiple transactions and the trail went cold — a preview of the laundering patterns that would become systematized over the following decade.

The incident transformed the Bitcoin community's security discourse. Before June 2011, the dominant narrative — propagated in BitcoinTalk discussions, early media coverage, and the Bitcoin.org website — was that Bitcoin's cryptographic design made it inherently secure. After the Allinvain theft, and the subsequent wave of wallet.dat-targeting attacks through 2011-2014, the narrative shifted to "your Bitcoin is only as secure as the computer your wallet.dat file lives on." This shift directly motivated:

The development and promotion of Bitcoin Core's wallet-encryption feature (encryptwallet, already implemented but underutilized)
The emergence of cold-storage practices (offline key generation, air-gapped signing)
The eventual development of hardware wallets (Trezor, 2014; Ledger, 2014)
The recognition that endpoint security, not blockchain cryptography, was the load-bearing security surface for individual holders

The Allinvain theft is also the earliest documented case where blockchain forensics was used by community members (not law enforcement) to trace stolen funds — a precursor to the on-chain forensic practices that would professionalize through 2015-2020 with the emergence of Chainalysis, Elliptic, and TRM Labs.

Timeline (UTC unless noted)

When	Event	OAK ref
Pre-2011-06	Allinvain accumulates ~25,000 BTC through early GPU mining; stores the `wallet.dat` file on a Windows PC without encryption	(standing T15.004 surface — unencrypted wallet file)
2011-06-13	Allinvain posts on BitcoinTalk: "I just got hacked — 25,000 BTC stolen"; the first publicly documented single-user BTC theft of meaningful magnitude	T15.004 (credential compromise — wallet.dat extraction)
2011-06-13 onward	BitcoinTalk community members trace the stolen BTC through blockchain transactions; trail goes cold after multiple hops	(community forensic effort — early on-chain tracing)
2011-06 → 2011-12	Second wave of wallet.dat-targeting thefts follows the Allinvain template; Bitcoin community begins shifting security discourse from "Bitcoin cryptography is secure" to "endpoint security is the relevant surface"	(paradigm shift — endpoint-security awareness)
2011–2014	Infostealer malware targeting `wallet.dat` files becomes a recognized attack class; Bitcoin Core wallet encryption adoption accelerates; cold-storage and air-gapped signing practices enter community discourse	(defender-side evolution)
Continuing	Allinvain's 25,000 BTC remain unrecovered and the attacker(s) remain unidentified through the OAK v0.1 cutoff	(unresolved — canonical unattributed early-Bitcoin theft)

Realised extraction

Full loss. Approximately 25,000 BTC were extracted from the victim's wallet.dat file and transferred to attacker-controlled addresses. None of the stolen Bitcoin has been recovered through the OAK v0.1 cutoff. The attacker(s) were never publicly identified. The extraction was permanent and complete — the victim received no recovery, no insurance, no law-enforcement restitution.

What defenders observed

Pre-event: the victim's Bitcoin private keys were stored in an unencrypted wallet.dat file on a Windows PC connected to the internet. The OAK lesson is that unencrypted-wallet-file-on-internet-connected-machine was, by mid-2011, the dominant storage posture for early Bitcoin miners who had accumulated holdings through low-difficulty GPU mining. Bitcoin Core had an encryptwallet feature, but it was optional and underutilized. The defender-side evolution from "unencrypted wallet file on internet-connected PC" to "encrypted wallet + cold storage + hardware wallet" was directly motivated by the Allinvain-class thefts of 2011-2012.
At-event: the theft was detected by the victim, not by any automated monitoring system. The victim noticed the missing BTC upon checking their wallet balance. The OAK lesson is that endpoint-compromise-to-private-key-extraction produces no on-chain pre-extraction signal — the theft manifests as a completed transaction from the victim's address, indistinguishable from a legitimate user-initiated send until the victim checks their balance.
Post-event: the BitcoinTalk community performed ad-hoc blockchain forensics to trace the stolen funds, establishing (in primitive form) the community-forensic-response pattern that would later professionalize into Chainalysis / Elliptic / TRM Labs. The community tracing efforts followed the stolen BTC through multiple hops before losing the trail — a preview of the laundering-hop pattern that T7.001-T7.003 would later systematize.
Post-event (paradigm shift): the Allinvain theft, combined with the June 19, 2011 Mt. Gox auditor-account compromise that followed six days later, created a concentrated June 2011 security-crisis window that permanently transformed the Bitcoin community's security discourse. The "two June 2011 incidents" — Allinvain (individual endpoint compromise) and Mt. Gox auditor account (exchange-privileged-account compromise) — together established the two foundational theft templates that would dominate crypto-asset attacks for the next 15 years.

What this example tells contributors writing future Technique pages

Allinvain is the foundational anchor for T15.004 (Credential Compromise) in the individual-holder context. Every subsequent endpoint-compromise-to-private-key-extraction attack — from clipboard hijackers to infostealer malware to EDR-bypass techniques — traces its lineage to the Allinvain template. Contributors writing T15.004 sub-techniques or future endpoint-compromise classification should cite Allinvain as the chronological anchor.
The June 2011 security-crisis window is a concentrated historical-reference window. Allinvain (June 13) + Mt. Gox auditor account (June 19) created a six-day concentrated security-crisis window that established the individual-endpoint and exchange-privileged-account theft templates simultaneously. Contributors writing historical-reference sections should treat the two incidents as paired foundational anchors.
Unattributed early-Bitcoin thefts are a distinct attribution category. The Allinvain theft is unattributed — no public law-enforcement disposition, no named-individual attribution, no public forensic attribution to a known cluster. This is the expected attribution state for pre-2013 individual-holder Bitcoin thefts where the forensic infrastructure (Chainalysis-class attribution graphs, exchange KYC records for off-ramp tracing) did not yet exist. Contributors writing attribution-strength analysis for pre-2013 cases should preserve unattributed as a distinct, honest category.

Public references

[allinvainbitcointalk2011] — Allinvain. "I just got hacked — 25,000 BTC stolen." BitcoinTalk forum, June 13, 2011. Primary-source contemporaneous victim disclosure: https://bitcointalk.org/index.php?topic=16457.0
[bitcointalksecurity2011] — BitcoinTalk forum. Security discussion threads, June 2011. Contemporaneous community response to the Allinvain theft, including early blockchain-tracing efforts and wallet-security recommendations.
[bitcoinmagazineallinvain2012] — Bitcoin Magazine. "A History of Bitcoin Hacks." 2012 (retrospective coverage of the 2011 thefts including Allinvain).
[chainalysishistory] — Chainalysis. Crypto Crime Report (various years). References to early Bitcoin theft patterns; the Allinvain case is cited in historical context as the first documented single-user Bitcoin theft.
[narayanantextbook] — Narayanan, Bonneau, Felten, Miller, and Goldfeder. Bitcoin and Cryptocurrency Technologies, Princeton University Press, 2016. Discussion of early Bitcoin security incidents in the context of endpoint-security and key-management practices.

Discussion

The Allinvain theft of June 13, 2011 is the foundational individual-endpoint-compromise anchor on the OAK public record. It established the template — unencrypted wallet file on internet-connected endpoint, attacker access via malware or remote-access vulnerability, complete extraction with no recovery — that would define individual-holder crypto theft for the next decade and a half. Every subsequent endpoint-to-private-key extraction class, from commodity infostealers (RedLine, Vidar, Raccoon Stealer) to targeted EDR-bypass credential-access techniques, traces its operational lineage to the Allinvain template.

The incident's structural significance is amplified by its timing: the Allinvain theft (June 13) and the Mt. Gox auditor-account compromise (June 19) occurred within six days of each other, creating a concentrated June 2011 security-crisis window that established both the individual-endpoint and exchange-privileged-account theft templates simultaneously. The Bitcoin community's security discourse shifted permanently within this window — from "Bitcoin's cryptography makes it secure" to "Bitcoin's security depends on the endpoint and the custodian."

The case's attribution surface — unattributed through the OAK v0.1 cutoff — is the expected state for pre-2013 individual-holder Bitcoin thefts. The forensic infrastructure that enables modern attribution (Chainalysis Reactor, TRM Forensics, Elliptic Investigator; exchange KYC off-ramp tracing; cluster-attribution graphs) did not exist in 2011. The Allinvain theft is the canonical example of why unattributed must be preserved as a distinct, honest attribution category for early-Bitcoin cases.