What happened
Finzly Corp, a financial services organization, was targeted by the N0n ransomware group in an attack identified on October 19, 2026. The breach resulted in the exposure of critical network configuration data and payment infrastructure secrets.
Why this matters
This incident highlights the catastrophic risk of storing infrastructure secrets and access keys in accessible formats. When threat actors gain access to cloud topology and payment secrets, they can pivot through internal networks, intercept financial transactions, and maintain persistence within the victim's environment, leading to long-term operational and financial damage.
How zero-knowledge changes this
SecureIDsafe’s zero-knowledge architecture would have neutralized the impact of this breach. By utilizing AES-256 client-side encryption, all sensitive infrastructure secrets and access keys would be stored as ciphertext that only the user can decrypt. Because SecureIDsafe never holds the encryption keys—which are derived locally on the user's device—a breach of the provider's storage would yield only useless, encrypted data to the attackers. Even if the N0n group gained access to the underlying storage environment, they would be unable to read the payment infrastructure secrets or cloud keys, as they lack the device-derived keys required for decryption. Furthermore, our non-bypassable 24-word BIP-39 seed recovery ensures that even in the event of a total system compromise, the user maintains sole custody of their data, preventing unauthorized access to the credentials that secure their most critical assets.