- Home
- Security
- One Missing Line of Code Drained 374 Crypto Wallets: Inside the SecondFi Signing Flaw That Exposed Every Transaction
One Missing Line of Code Drained 374 Crypto Wallets: Inside the SecondFi Signing Flaw That Exposed Every Transaction

Between June 21 and 23, 2026, attackers drained roughly 16 million ADA — worth approximately 2.4 million USD — from 374 wallets connected to the SecondFi platform on Cardano. The cause was not a bridge hack, a smart contract bug, or a phishing scam. It was a single missing line of code in a wallet update that turned every transaction its users ever signed into a public disclosure of their private keys.
By Elena Kowalski | July 11, 2026
Table of Contents
The Hook: One Update, 374 Empty Wallets
On June 8, 2026, SecondFi pushed version 10.0.3 of its Android app to the Google Play Store. It looked like a routine update. Nobody — not the users who installed it, not the security researchers who monitor Cardano, not the platform's own team — realized that the new signing code was broken in a way that would prove catastrophic.
The problem centered on something called a nonce — a secret random number that encryption systems use when signing transactions. Think of it like a one-time pad that makes each digital signature unique and impossible to reverse-engineer. Every cryptography textbook in the world hammers home the same rule: the nonce must be unpredictable and must never be reused or derived from anything an attacker can see.
SecondFi's Android 10.0.3 signer derived its nonce entirely from public transaction data — information that anyone can read directly from the blockchain. That meant a single signature from any affected wallet was enough for an attacker to reconstruct the private key. No device access required. No phishing. No social engineering. Just reading what was already sitting on-chain.
On-Chain Evidence: How the Drain Unfolded
The first exposure happened on June 12, when a user at a Cardano address signed a routine spend of approximately 1 million ADA through the buggy signer. The funds did not disappear that day. But the private key behind that transaction was now effectively public — anyone who knew what to look for could reconstruct it from the blockchain record.
Nine days later, the first wave of attacks began.
- June 21-23 — Two independent attacker groups swept through 374 wallets in three automated waves
- Attacker A — Hit 171 addresses in two automated batches
- Attacker B — Swept 203 addresses in a separate automated campaign
- Total damage — Approximately 16 million ADA, equivalent to roughly 2.4 million USD at the time
SlowMist founder Cos, who monitored the drain in real time, observed that the attacker appeared to have obtained a batch of private keys in advance and worked through them continuously for over 30 hours. The amounts drained decreased from large to small — a pattern consistent with an attacker working through a pre-compiled list of compromised keys.
Charles Guillemet, a prominent security researcher, independently verified the exploit by pulling signatures from Cardano mainnet and rebuilding private keys from a single on-chain signature each. He confirmed the mechanism worked across every address he tested. No special tooling. No device access. Just public blockchain data and math.
The Core Conflict: A Software Bug Disguised as a Hacking Story
What makes this incident different from the typical crypto hack headline is that no contract was exploited, no bridge was manipulated, and no developer was phished. The blockchain worked exactly as designed. The Cardano network was never attacked. It was simply read.
The vulnerability was introduced through a software update — the kind that most users install automatically without a second thought. Every transaction signed through the broken signer was a standing disclosure. Users who had generated their seed phrases in other wallets (like Daedalus or Yoroi) and later imported them into SecondFi were also affected if they signed anything after the update.
Taylor Monahan, one of the most respected names in wallet security, called the vulnerability worse than 2011-era Bitcoin wallet flaws — a comparison that carries enormous weight among security professionals, given that early Bitcoin wallets were notorious for catastrophic key leakage bugs.
Then came a second controversy. As an emergency measure, SecondFi moved approximately 129 million ADA — far more than what was stolen — to an undisclosed third-party custodian. The platform described this as a rescue operation to protect remaining funds from further attacks. But the custodian's identity was not revealed, and no return framework was announced at the time. For users already reeling from the discovery that their keys had been silently exposed, the news that their remaining assets had been moved to an unknown destination added a new layer of anxiety.
Market Implications: What This Means for Wallet Safety
The SecondFi incident exposes an uncomfortable truth that most crypto investors would rather not think about: the security of your funds depends not just on the blockchain, but on the wallet software you use to interact with it. A perfectly designed blockchain with flawless cryptography can still be undermined by a single buggy app update.
This is not a Cardano-specific problem. The same class of vulnerability — nonce reuse or weak nonce derivation — has affected wallets across Bitcoin, Ethereum, and virtually every other blockchain over the years. The underlying math is universal. Ed25519, the signature scheme used by Cardano, is considered cryptographically sound when implemented correctly. The failure was in the implementation, not the algorithm.
For regular investors, the implications are sobering:
- Updates carry risk — A routine app update can introduce critical vulnerabilities. Users who delayed updating had their keys remain safe, while those who updated promptly were exposed.
- Hardware wallets matter — This exploit only affected software wallets where signing happens on a device that could run buggy code. Hardware wallets isolate signing in dedicated hardware, making this class of attack impossible.
- Transparency is essential — SecondFi's response was criticized for being slow and vague. The initial June 22 statement described "a security issue affecting a small number of wallets," language that dramatically understated the scope of the problem.
- Custodial rescues cut both ways — Moving 129 million ADA to an unnamed custodian may have prevented further theft, but it also meant users lost direct control of their remaining assets with no clear timeline for return.
The Verdict: Trust the Chain, Question the App
EMURGO, which describes itself as a co-founding entity of Cardano and is listed as the developer behind the SecondFi app, pledged to return assets to all affected wallet addresses. A patch was confirmed on June 24. But none of these measures can undo the fundamental issue: the compromised signatures remain on the blockchain forever, and any private key that was exposed during the two-week vulnerability window cannot be "un-exposed."
The SecondFi exploit is a masterclass in why implementation security — the unglamorous, easily overlooked details of how wallet software actually handles cryptographic operations — matters just as much as the blockchain protocol itself. A single missing line of code in an app update quietly turned 374 wallets into open books. No alarm bells rang. No security audit caught it. The blockchain recorded every signature exactly as designed, and that is precisely what made the exploit possible.
For anyone holding cryptocurrency, the lesson is straightforward: use a hardware wallet for significant holdings, be cautious with software updates, and remember that the weakest link in your security setup is almost never the blockchain itself — it is the software layer sitting between you and it. The Cardano network did not fail. A wallet app did. And in crypto, that distinction can be the difference between keeping your funds and watching them drain in real time.
The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.
Disclaimer: This article is for informational purposes only and does not constitute financial advice. Cryptocurrency investments carry risk; always do your own research.
25 Comments