EMURGO CEO Phillip Pong announced that the company has completed the development of a refund mechanism for affected SecondFi users. The payout process is planned to launch in approximately two weeks — the first week will be spent finalizing the algorithm, and the second on thorough testing.

As a reminder, as a result of the exploit affecting 374 addresses, attackers withdrew approximately 16 million ADA (at that time — about $2.4 million). Chain analysis shows that the attack was systemic in nature, rather than an accidental leak.

SecondFi has already urged users not to make any asset transfers and to trust only official instructions. The team specifically warned about a wave of fraudulent messages, emphasizing that the service never requests private keys, seed phrases, or wallet access.

According to SecondFi, four incidents occurred between June 21 and 23. In three cases, external attackers withdrew funds from 374 addresses. In the fourth episode, the team urgently transferred about 129 million ADA to an independent custodian to isolate the assets. Verification of these funds is currently being conducted by an external audit firm.

The company identified two attacker wallets: one linked to 171 compromised wallets, the second to 203. Approximately 4 million ADA associated with the theft remain at a flagged collection address and are under surveillance. Law enforcement agencies have already been notified.

A separate investigation by Tibane Labs sheds light on the technical nature of the vulnerability. According to their version, the issue was not nonce reuse, but an Ed25519 signing error. They claim that on June 8, an unaudited trantor SDK published on npm by an independent developer replaced the previously used verified EMURGO signing module. In their assessment, a single signed message was sufficient to recover the private key.

Notably, EMURGO has not yet published a full technical post-mortem and has not publicly responded to Tibane Labs' findings. This raises questions about the transparency of the investigation, especially given that SecondFi (until April — Yoroi) has long remained one of the primary wallets in the Cardano ecosystem, and EMURGO is one of the three founding organizations of the network.

Against the backdrop of this incident, it is worth noting that in the second quarter of 2026, the crypto industry set an anti-record for the number of hacks — 83 incidents with total losses of $755.3 million. This points to a systemic security problem in the industry, where even top-tier projects are not immune to errors in the software supply chain.

Analyst's opinion: This case underscores the critical importance of auditing all used libraries and dependencies. Replacing one module in an SDK can lead to catastrophic consequences, and EMURGO needs not only to return the funds but also to provide a comprehensive technical report to restore the trust of the Cardano community.