Chainstack Security Incident: How to Rotate Node Credentials and API Keys
Chainstack disclosed that an attacker reached its production systems in late October 2026, possibly exposing customer details, password hashes and node credentials. Here is what to do now.
Crypto Support & Research Desk
Quick answer: Blockchain node provider Chainstack disclosed on November 3, 2026 that an attacker accessed parts of its infrastructure, including a database with customer names, emails and password hashes, and systems holding node credentials. On November 10 it published technical indicators. Customers should change passwords, rotate node credentials and regenerate platform API keys now.
What happened
Chainstack, which provides RPC endpoints and managed nodes for Ethereum, Solana, Base and many other networks, published an official security incident notice on November 3, 2026. According to the timeline in that notice:
- October 26: the attacker entered a development environment through an internet-exposed test Grafana instance that still used default admin credentials.
- October 29: the attacker reached production, reading cloud and Kubernetes secrets.
- October 31: Chainstack detected the intrusion and cut the access paths the same day.
- November 2: the investigation was closed; the last observed use of a copied credential was at 06:28 UTC.
- November 3: initial public disclosure and emails to customers.
- November 10: Chainstack added a technical details section with indicators of compromise for security teams.
Chainstack says there is "no evidence that a software vulnerability was exploited". Instead, the attack chained default credentials, exposed admin functions, an internal tool server without authentication, over-broad permissions and long-lived credentials. Chainstack assesses with high confidence that the attacker used ARTEX, an open-source framework that coordinates AI agents, and links the intrusion to a broader AI-powered campaign reported in late October. It says it is attributing the tooling, not a specific threat actor.
What data was affected
According to Chainstack's notice:
- Customer account information in one database may have been exposed: organization names, account holder names, emails of organization members and password hashes.
- Node credentials: the attacker had access to systems that hold them. Chainstack says it has no evidence they were read, but asks customers to treat them as exposed.
- Payment card details are not stored by Chainstack and were not exposed.
- Customer nodes, console and API were checked and were not modified.
Secondary coverage, including Start with Identity, describes the hashes as taken. Chainstack's own wording is more cautious ("may have been exposed"). The number of affected customers has not been published.
Who is affected
- Developers and teams with Chainstack accounts, including those running dApps, bots, indexers or back-end services on Chainstack endpoints.
- Projects that embed Chainstack endpoints in apps or scripts. An exposed endpoint credential could be used to consume your request quota or to read data through your endpoint.
- End users of apps built on Chainstack. They are not directly exposed, but they should watch for phishing that uses the incident as a hook.
Step-by-step: what Chainstack customers should do
1. Change your Chainstack password
Change your password from the official console. If you reused that password anywhere else, change it there too. Password hashes are designed to be hard to reverse, but weak or reused passwords are at greater risk.
2. Rotate node credentials
Chainstack offers self-service credential rotation in the console. Its notice says current endpoints keep working until you complete rotation, so you can update your apps without downtime. Chainstack's endpoint security guide explains that rotation replaces the auth token, username, password and x-token together. A multichain auth token cannot be rotated; the guide says to create a new multichain endpoint and switch to it.
3. Regenerate platform API keys
If you use the Chainstack platform API to manage nodes programmatically, regenerate your API keys and update every service, CI pipeline and secret store that uses them.
4. Enable two-factor authentication
The incident notice does not mention 2FA, but Chainstack's general security guidance recommends enabling it under Settings, then Security. Use an authenticator app rather than SMS.
5. Tighten endpoint access rules
- Add IP allowlists, origin allowlists or referrer rules where available.
- Keep endpoint secrets out of front-end code. Proxy requests through your own back end.
- Use separate endpoints for development, staging and production.
- Review team members and roles, and remove accounts that no longer need access.
6. Check usage for anomalies
Review request volumes and billing for spikes since late October. Unexpected traffic could indicate someone used an exposed credential.
How to verify you are dealing with the real Chainstack
Chainstack says it will never ask for passwords, tokens or keys, and that it is emailing all customers about the incident. Phishing campaigns often follow breach disclosures, especially when attackers have names and emails.
- Log in by typing the Chainstack console address yourself, not through email links.
- Treat any email or message asking you to "verify" credentials, share API keys or install software as suspicious.
- Compare any indicators you find in your own logs with the full list on Chainstack's official notice.
What users of crypto apps should know
If you use a wallet or dApp that may rely on Chainstack, there is no indication from Chainstack that funds were affected. The bigger risk for ordinary users is social engineering. Breaches that leak names and emails are often followed by targeted scams, similar to the patterns we covered in the Revolut data breach claim and in fake AI trading agent malware. Be suspicious of unexpected emails about "account security" and do not download tools or browser extensions from links in messages.
Infrastructure incidents are also a reminder that blockchain services depend on many layers. When a chain or provider has problems, transfers can stall, as with the recent Initia L1 halt. Keep official status pages bookmarked so you can check quickly.
What to avoid
- Do not delay credential rotation because endpoints still work. Old credentials remain valid until you rotate.
- Do not paste API keys or endpoint URLs with embedded tokens into public repositories, chats or support tickets.
- Do not reuse your Chainstack password on any other service.
- Do not trust third-party "breach checker" sites that ask for your credentials.
Frequently asked questions
Was my crypto wallet affected by the Chainstack breach?
Chainstack's notice does not say that any wallet keys or user funds were affected. Node credentials control access to RPC endpoints, not to wallets. Stay alert for phishing that uses the breach as a pretext.
What data did the attacker access at Chainstack?
Chainstack says organization names, account holder names, member emails and password hashes may have been exposed. The attacker also had access to systems holding node credentials; Chainstack has no evidence they were read but treats them as exposed. Payment card details are not stored.
Will rotating my Chainstack node credentials cause downtime?
According to Chainstack, current endpoints keep working until you complete rotation, so you can update your applications first. Multichain auth tokens cannot be rotated and need a new endpoint instead.
When did the Chainstack incident happen?
Chainstack says the attacker first entered on October 26, 2026, reached production on October 29 and was detected and cut off on October 31. It disclosed the incident on November 3 and added technical indicators on November 10.
Conclusion
The Chainstack incident did not, according to the company, touch customer nodes or funds, but it may have exposed account details and node credentials. If you have a Chainstack account, change your password, rotate node credentials, regenerate API keys, enable 2FA and lock down endpoint access rules today. Everyone else should treat unexpected "security" emails with caution and never share wallet secrets.
This article is for general information only and is not security, legal or financial advice. Blockchain Support USA is an independent publication and is not affiliated with Chainstack, any exchange or any node provider. We will never ask for your recovery phrase, private keys, passwords or 2FA codes.
Regulatory & Financial Risk Disclosure
The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.
About the Author
Crypto Support & Research Desk
Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.