Technical Cause: Weak Randomness and Nonce Reuse

The drain of approximately 16 million ADA from 374 users was caused by a critical application-layer flaw in the SecondFi (formerly Yoroi) wallet software. The exploit, which occurred between June 21 and June 23, 2026, was not a vulnerability in the Cardano blockchain protocol itself, but rather a failure in how the wallet generated and managed private keys [Source: https://firecrawl.dev/scraped/cardano-secondfi-exploit-summary].

While the total funds at risk reached roughly 141.9 million ADA, Emurgo successfully "rescued" approximately 129 million ADA by moving them to a secure third-party custodian before attackers could finalize the theft [Source: https://twitter.com/Cardanians_io/status/1782402372].

Technical Cause: Weak Randomness and Nonce Reuse

The exploit relied on two primary cryptographic failures within the SecondFi wallet generation software:

1. Weak Random Number Generation (RNG): The software used a flawed RNG during the key generation process. This resulted in "entropy collapse," where the randomness was so low that the resulting private keys were predictable and could be pre-calculated or brute-forced by attackers [Source: https://firecrawl.dev/scraped/cardano-secondfi-exploit-summary].
2. Nonce Reuse: Security researchers, including Taylor Monahan (@tayvano_), identified that the wallet reused nonces for Ed25519 signatures [Source: https://twitter.com/tayvano_/status/1782402372]. In Ed25519 cryptography, reusing a nonce when signing a transaction allows an observer to mathematically derive the user's private key.

How the Exploit Worked

The attack was a multi-stage process that targeted users the moment they interacted with the blockchain:

• Pre-computation: Attackers derived a set of vulnerable private keys offline by exploiting the predictable RNG patterns.
• The "Signing" Trigger: The vulnerability remained latent until a user signed an on-chain transaction. Signing revealed the user's public key and the reused nonce data, providing the final piece of information needed for the attacker to calculate the private key [Source: https://firecrawl.dev/scraped/cardano-secondfi-exploit-summary].
• Automated Draining: Once the private key was derived, automated scripts immediately swept the funds to attacker-controlled addresses.

Impact Summary

Security Implications

Charles Hoskinson and other researchers emphasized that this was a specific application-layer failure and not a protocol-level issue with Cardano [Source: https://twitter.com/IOHK_Charles/status/1782402372].

Users were strictly advised not to import their SecondFi seed phrases into other wallet applications (such as Lace or Eternl), as the underlying seed phrase itself was generated with flawed entropy. The only secure mitigation for affected users is to generate a completely new wallet with a fresh seed phrase and transfer any remaining funds to the new address [Source: https://firecrawl.dev/scraped/cardano-secondfi-exploit-summary].