Technology
Ars Technica - All content

Chainalysis says hackers stole credentials and tokens for all of its customers

Source Entity

Dan Goodin

November 7, 2026
Chainalysis says hackers stole credentials and tokens for all of its customers

Two major firms, Gnosis Pay and Chainalysis, have reported significant data breaches involving sensitive customer and financial information. While Gnosis Pay confirms funds remain secure, the Chainalysis incident raises concerns due to the exposure of credentials for high-profile government and private sector clients.

Cybersecurity Crisis: Gnosis Pay and Chainalysis Breaches

The financial and blockchain sectors are reeling following simultaneous security disclosures from Gnosis Pay and Chainalysis. These incidents underscore the persistent vulnerability of digital infrastructure, even among entities tasked with oversight and secure payment processing. While both companies have initiated containment protocols, the nature of the data exposed poses significant risks to their respective user bases.

Gnosis Pay: Legacy System Vulnerabilities

On November 3, Gnosis Pay identified unauthorized access to its legacy consumer card system. The breach, which was contained within two hours, resulted in the exposure of highly sensitive information, including full payment card numbers, CVV codes, expiration dates, and physical home addresses. Despite the compromise of this data, Gnosis Pay has explicitly stated that actual customer funds remain secure and that their enterprise-grade white-label platform was not involved in the incident. This highlights the dangers of maintaining legacy infrastructure, which often serves as a weak point in otherwise modern fintech ecosystems.

The Chainalysis Security Breach

In a parallel development, blockchain analysis firm Chainalysis confirmed a sophisticated "multifront cyberattack" occurring in October. Hackers successfully obtained names, usernames, password hashes, and live tokens for their entire user base. Because Chainalysis serves a high-profile clientele—including the FBI, the U.S. Air Force, and major institutions like Microsoft and Coinbase—this breach represents a significant security hurdle. The use of AI-driven tactics and on-path data interception suggests a highly capable threat actor, potentially a state-sponsored or advanced persistent threat (APT) group.

Broader Implications for Digital Finance

The exposure of crypto wallet addresses alongside personal identification data creates a dangerous intersection for users. When hackers possess both a home address and a linked crypto wallet, they gain the ability to conduct targeted phishing, social engineering, or even physical extortion. For firms like Chainalysis, the loss of login credentials for government agencies introduces a geopolitical dimension to the breach, as the attackers now possess the keys to platforms that monitor illicit blockchain activity.

Historical Context and Future Trends

These events mirror a growing trend of cyberattacks targeting the "pipes" of the crypto economy. As decentralized finance (DeFi) and traditional financial services converge, the attack surface for bad actors has expanded exponentially. Historically, attackers focused on protocol exploits; however, these recent breaches demonstrate a shift toward targeting the service providers themselves. Future trends will likely necessitate a move toward zero-trust architectures and mandatory multi-factor authentication (MFA) standards, as static credentials and legacy system vulnerabilities become increasingly untenable in the modern threat landscape.

Conclusion

While both Gnosis Pay and Chainalysis have acted to contain these incidents, the fallout remains significant. The integrity of financial data is the bedrock of digital trust. As these companies navigate the recovery process, the industry must re-evaluate its reliance on legacy systems and the security of internal data handling, ensuring that the next generation of financial technology is built with resilience at its core.

Verification Required?

Read the full report from the primary source

Go to Ars Technica - All content