{"type":"rich","version":"1.0","author_name":"whit (npub14d…w0xv0)","author_url":"https://nostr.ae/npub14d7ezuzsy55f6c2f4k02r27yeexyj42a7uvsfu53xmpzx7z75mmsnw0xv0","provider_name":"njump","provider_url":"https://nostr.ae","html":"🧾 COLDCARD: WHAT HAPPENED, WHO IS INVOLVED \u0026 WHAT PLEBS SHOULD DO\n\nColor code\n\n🟦 CODE / PRODUCT\n🟨 WARNING / INVESTIGATION\n🟧 PUBLIC COMMUNICATION\n🟩 CONFIRMED / FIX / RESPONSE\n🟥 THEFT / ATTACKER ACTIVITY\n💔 VICTIM ACTION\n⬜ UNKNOWN / NEED MORE EVIDENCE\n\nImportant: A person’s name appears because they have a documented role in the product, investigation, research, communication, or response. That does not mean they caused the vulnerability or participated in the theft. The attackers remain unidentified.\n\n⸻\n\n🟦 2021: THE VULNERABILITY ENTERS THE PRODUCT\n\nJanuary–March 2021\n\nColdcard integrates libNgU into its firmware.\n\nPeople/projects relevant to this stage:\n\nswitck #libNgU\nPeter D. Gray / doc-hex #ColdcardFirmware\nColdcard/Coinkite developers #Development\n\nThe critical integration ultimately allowed wallet seed generation to reach a deterministic software PRNG rather than the intended hardware random-number generator.\n\nFor affected older Mk2/Mk3 devices, later analysis puts effective entropy around 40 bits instead of the intended 128 bits. \n\nThat turns an astronomically large seed-search problem into something attackers can potentially enumerate.\n\n⸻\n\n🟦 MARCH 1, 2021: THE CRITICAL CODE PATH CHANGES\n\nColdcard seed generation moves into the new RNG architecture.\n\nThe later reconstruction is essentially:\n\nGenerate seed\n\n↓\n\nrandom.bytes()\n\n↓\n\nngu.random.bytes()\n\n↓\n\nwrong rng_get() implementation\n\n↓\n\nsoftware PRNG\n\n↓\n\npredictable-enough seed space\n\n⬜ Questions still worth answering:\n\nWho reviewed this specific change?\n\nWas RNG behavior tested on actual production hardware?\n\nWho verified which rng_get() implementation ended up in the finished binary?\n\n⸻\n\n🟦 MARCH 17, 2021: FIRMWARE 4.0.0 SHIPS\n\nColdcard itself described the release as containing major internal cryptographic/BIP39 changes.\n\nPeople relevant organizationally:\n\nRodolfo Novak / NVK #CoinkiteLeadership\nPeter D. Gray / doc-hex #ColdcardFirmware\nswitck #libNgU\n\nAgain, leadership involvement doesn’t establish authorship of the vulnerable code.\n\n⸻\n\n🟨 MARCH 29, 2021: ANOTHER SECURITY ISSUE IS FIXED\n\nColdcard 4.0.1 fixes a security problem in 4.0.0.\n\nWe have not established that this was the RNG problem.\n\n⬜ But it creates an important historical question:\n\nAfter finding a security problem immediately following a major cryptographic rewrite, was the rest of that rewrite comprehensively reviewed?\n\n⸻\n\n⏳ 2021 → 2026: THE FIVE-YEAR GAP\n\nThis is one of the central mysteries.\n\nThe vulnerable code exists.\n\nThe source is public.\n\nColdcard continues being used.\n\nPeople generate wallets.\n\nYet the entropy defect apparently remains undetected.\n\nThis is why:\n\nOpen source means people CAN inspect code. It doesn’t mean somebody DID successfully verify every security-critical path.\n\n⸻\n\n⬜ 2021/22: CLAIMED EARLIER WARNING\n\nJames O’Beirne #RNGResearch reportedly later said another person had raised an earlier concern.\n\nWe still need the original communication before treating that as established notice.\n\nStatus: LEAD, NOT CONCLUSION.\n\n⸻\n\n⬜ 2022: REPORTED SECURITY REVIEW\n\nThere are claims concerning an outside security review containing RNG-related recommendations.\n\nThe original report remains important evidence to obtain.\n\nQuestions:\n\nWhat exactly did it say?\n\nWho received it?\n\nWhat recommendations were implemented?\n\n⸻\n\n🟨 MAY 2025: O’BEIRNE SAYS HE RAISES RNG CONCERNS\n\nJames O’Beirne #RNGResearch\n\nO’Beirne says he examined the Coldcard RNG architecture, became concerned and raised the matter with Coinkite.\n\n⬜ The crucial missing evidence remains the original May 2025 correspondence.\n\nThere is an enormous difference between:\n\n“I don’t like this library.”\n\nand:\n\n“Your seed generator may not actually be using the hardware RNG.”\n\nUntil we see the communication, don’t collapse those possibilities together.\n\n⸻\n\n⬜ JUNE 2026: REPORTED AI-ASSISTED SECURITY REVIEW\n\nA review shortly before the attack has been reported.\n\nWhat we need:\n\nscope\n\nfindings\n\nprompts\n\nRNG coverage\n\nseed-generation coverage\n\nUntil those records are available, this remains an investigative question rather than proof someone missed a known vulnerability.\n\n⸻\n\n🟥 JULY 30, 2026: THE BITCOIN STARTS MOVING\n\nUNKNOWN ATTACKER(S) #UnknownAttackers\n\nAttackers apparently enumerate vulnerable Coldcard-generated seeds offline, derive addresses and sweep wallets.\n\nThey don’t need to steal the physical Coldcard.\n\nThey don’t need the victim to plug it in.\n\nThey don’t necessarily need to phish the victim.\n\nThey can attack the weak seed itself.\n\nGalaxy now confirms attackers began exploiting affected wallets at least by the early morning of July 30. \n\n⸻\n\n🟨 JULY 30: PLEBS START SOUNDING THE ALARM\n\nVictims report unexpected wallet drains.\n\nThen investigators begin connecting apparently unrelated cases.\n\nKevin Loaec #EarlyWarning\n\nwarns Coldcard users to check balances.\n\n↓\n\nRodolfo Novak / NVK #CoinkiteResponse\n\ninitially expresses skepticism that the reports demonstrate a systemic Coldcard failure.\n\n↓\n\nRob Hamilton #OnChainInvestigation\n\nexamines blockchain activity and identifies a larger pattern.\n\n↓\n\nKevin Loaec #RNGResearch\n\nmoves toward the weak-entropy hypothesis.\n\n↓\n\nJames O’Beirne #UserWarning\n\npublicly warns affected users to move bitcoin.\n\n↓\n\nRodolfo Novak / NVK #CoinkiteResponse\n\nchanges his public position as evidence accumulates and Coinkite investigates.\n\n↓\n\nGreg Sanders / instagibbs #TechnicalReproduction\n\nindependently reproduces/demonstrates the technical failure.\n\nThat’s the critical transition:\n\n🟨 We think something is wrong\n\nbecomes\n\n🟩 We can reproduce what’s wrong.\n\n⸻\n\n🟩 JULY 30–31: COINKITE CONFIRMS THE ENTROPY PROBLEM\n\nEmergency remediation follows.\n\nAnd here’s the thing every pleb needs burned into memory:\n\nUpdating firmware does NOT fix a vulnerable seed.\n\nThe weakness is embedded in the seed that already exists.\n\nA vulnerable wallet needs to be migrated to a newly generated safe seed, following current official guidance.\n\nThe newest reporting continues to describe the failure as a software PRNG being reached instead of the intended hardware entropy source. \n\n⸻\n\n🟧 THE WARNING NETWORK FORMS\n\nPeople helping communicate/respond include:\n\nMatt Odell / ODELL #UserWarning\n\nCalle #SecurityResponse\n\nBen Perrin / BTC Sessions #PublicEducation\n\nJames O’Beirne #RNGResearch\n\nKevin Loaec #EarlyWarning\n\nRob Hamilton #OnChainInvestigation\n\nGreg Sanders / instagibbs #TechnicalReproduction\n\nThey appear here because of their respective public roles.\n\nThey are not being identified as attackers.\n\n⸻\n\n🟥 JULY 30 → AUGUST 6: MULTIPLE ATTACKERS\n\nGalaxy has now confirmed something particularly important:\n\nThere wasn’t merely one identifiable attacker footprint.\n\nResearchers have identified at least 33 additional attacker footprints beyond the major waves and say with high confidence that multiple attackers were exploiting the vulnerability.\n\nThey cannot determine whether every footprint represents a different person. \n\nThat means don’t turn:\n\n“multiple attacker footprints”\n\ninto:\n\n“33 hackers.”\n\nWe don’t know that.\n\n⸻\n\n🟥 CURRENT CONFIRMED DAMAGE\n\nAs of Galaxy’s August 14 accounting:\n\n190 victims directly contacted\n\n8,600+ addresses\n\n1,778.84 BTC confirmed stolen\n\napproximately $112.7 million at the valuation Galaxy used.\n\nAnd importantly:\n\n1,531 BTC was still sitting unmoved in attacker-controlled addresses.\n\nApproximately 246 BTC had moved onward.\n\nOf those moved funds, about 65% entered CoinJoin transactions, while the remainder continued through other on-chain paths, sometimes peel chains. Small amounts reached exchanges or interchain bridges. \n\nGalaxy has supplied attacker-address information to exchanges, compliance companies, investigators and law enforcement so funds might be frozen if they reach centralized intermediaries. \n\nSo:\n\nStolen does NOT necessarily mean investigators should give up.\n\n⸻\n\n💔 NOW: “MY BITCOIN IS STILL THERE”\n\nThis person needs action, not investigation Twitter.\n\nFirst determine:\n\nColdcard model\n\nfirmware that generated the seed\n\napproximately when the seed was generated\n\nwhether dice entropy was added\n\nwhether a strong unique BIP39 passphrase exists\n\nwhether BIP85 child wallets were derived\n\nwhether multisig is involved\n\nThen follow the current official Coldcard migration instructions, not random screenshots or DMs.\n\nDo not simply:\n\nupdate firmware → keep same vulnerable seed → assume safe.\n\nThat misses the core problem.\n\n⸻\n\n💔 “MY BITCOIN IS ALREADY GONE”\n\nDo not wipe everything in panic.\n\nPreserve evidence.\n\nCreate a folder containing:\n\nColdcard information\n\nModel\nFirmware\nPurchase date\nApproximate seed-generation date\n\nWallet information\n\nPublic Bitcoin addresses\nTransaction history\nWhether singlesig/multisig\nWhether BIP85 was used\nWhether dice were used\nWhether a passphrase existed\n\nTheft information\n\nTXID\nDate/time\nAmount\nDestination address(es)\nScreenshots\n\nSupporting records\n\nColdcard purchase receipt\nExchange withdrawals showing how BTC reached the wallet\nRelevant support emails\nWarnings received\nCommunications concerning the incident\n\nBut:\n\n🚨 NEVER PUT THE SEED PHRASE IN THE EVIDENCE PACKET.\n\nAlso never send:\n\nBIP39 passphrase\n\nXPRV\n\nPIN\n\nprivate keys\n\ndice-roll sequence used to generate the wallet\n\nInvestigators generally need the public transaction evidence, not the secret required to spend what’s left.\n\n⸻\n\n🏛️ REPORT IT\n\nFor U.S. victims, the FBI explicitly asks cryptocurrency victims to report:\n\nwallet addresses\n\namounts\n\ntype of cryptocurrency\n\ntransaction hashes / TXIDs\n\ndates and times\n\nplus other identifying information surrounding the incident. \n\nFBI Internet Crime Complaint Center⁠\n\nVictims can also contact their local FBI field office. \n\nDon’t assume:\n\n“Bitcoin transactions can’t be reversed, therefore reporting is pointless.”\n\nBlockchain transactions themselves aren’t reversed, but tracing can identify centralized touchpoints, and exchanges can freeze assets through their own processes or legal process. \n\n⸻\n\n🚨 THE SECOND ROBBERY\n\nThis needs to become one of your loudest warnings.\n\nAfter somebody posts:\n\n“I lost 8 BTC.”\n\nThey may receive:\n\n“I can recover it.”\n\n“I work with law enforcement.”\n\n“I traced the hacker.”\n\n“Send me $5,000 and I’ll freeze the wallet.”\n\n“Connect your wallet here.”\n\n“Send your seed so I can verify whether you’re affected.”\n\nNO.\n\nThe FBI specifically warns that cryptocurrency recovery scammers target people who already lost crypto, including fake recovery companies and people pretending to have law-enforcement connections. \n\nPrivate recovery companies cannot issue seizure orders.\n\nLaw enforcement doesn’t charge victims an investigation fee. \n\nAnd the current IC3 homepage itself warns that scammers are impersonating IC3. \n\nNobody legitimately helping investigate this needs your seed phrase.\n\n⸻\n\n🧡 HOW ORDINARY PLEBS CAN HELP\n\nThis may be the most important part of the entire project.\n\nYou do not need to become a hacker.\n\nHelp find Coldcard owners who aren’t terminally online.\n\nThe person most endangered now may not be arguing about entropy on Nostr.\n\nIt may be someone who:\n\nbought a Coldcard in 2022\n\ngenerated a seed\n\nput bitcoin on it\n\nput the Coldcard in a drawer\n\nand thinks:\n\n“Hardware wallet. I’m good.”\n\nThose people need the warning.\n\nPlebs can also:\n\nArchive public evidence.\n\nPreserve URLs, dates, screenshots and original context.\n\nHelp victims organize evidence.\n\nDon’t ask for their seeds.\n\nPoint victims toward official reporting.\n\nDon’t promise recovery.\n\nTranslate the technical explanation into ordinary language.\n\nWeak randomness made some seeds guessable.\n\nThat’s enough for most people.\n\nWatch for recovery scammers.\n\nThey’re going to hunt the victim population.\n\nDon’t dox victims.\n\nKnowing that somebody owns substantial Bitcoin is itself dangerous information.\n\nDon’t accuse named people without evidence.\n\nDevelopers, executives, researchers, auditors, promoters and funders have different roles.\n\nRelationship ≠ responsibility.\n\nResponsibility ≠ criminality.\n\nCriminality requires evidence.\n\n⸻\n\n⚖️ AND KEEP OUR INVESTIGATION SEPARATE\n\nOur unanswered historical questions remain:\n\n⬜ Who reviewed the March 2021 RNG integration?\n\n⬜ What exactly happened during release security review?\n\n⬜ What was the unrelated 4.0.0 security issue?\n\n⬜ What did the reported 2022 review say about RNG?\n\n⬜ What exactly did James O’Beirne communicate in May 2025?\n\n⬜ Who received it?\n\n⬜ What was the scope of the reported June 2026 AI review?\n\n⬜ Were earlier unexplained wallet drains actually connected?\n\n⬜ Who were the attackers?\n\n⬜ Can centralized touchpoints eventually identify or freeze attacker funds?\n\nThose questions matter.\n\nBut they come after protecting people who may still be exposed.\n\n⸻\n\n🧾 THE ENTIRE THING IN SIX WORDS\n\nCHECK → MIGRATE → PRESERVE → REPORT → WARN → VERIFY\n\nAnd underneath that:\n\nDon’t trust a DM. Don’t share seeds. Don’t accuse without receipts.\n"}