Chainstack breach exposed customer account data and password hashes; rotate node credentials

Blockchain RPC provider Chainstack disclosed on Nov 3 2026 that an external attacker reached parts of its infrastructure through a third-party component, in what it links to a broader late-October AI-powered attack campaign. Access began in a development environment on Oct 26, reached some production systems on Oct 29, and was cut on Oct 31 after detection; the investigation closed Nov 2. The attacker accessed a database with organization names, account-holder names, member email addresses and password hashes, and had access to systems holding node credentials. Chainstack says it has no evidence node credentials were read but is treating them as exposed. Customer-facing services kept running; payment card details are not stored. Customers must change passwords, rotate node credentials (self-service in the console), regenerate platform API keys, and watch for phishing.

Why this severity: Customer account PII and password hashes accessed; node credentials treated as exposed though unread evidence is lacking

Started

Oct 26, 2026

• #Chainstack
• #Blockchain
• #Rpc
• Data breach
• #Credential Rotation
• #Third Party Vendor