Incidents

Chainstack Data Breach: Customers Urged to Reset Passwords and Rotate API Keys

An attacker accessed Chainstack's customer account database and part of its production environment. Rotate passwords, API keys and node credentials now.

Chainstack Data Breach: Customers Urged to Reset Passwords and Rotate API Keys

On November 3, Chainstack disclosed a breach affecting its customer account database. The blockchain infrastructure provider is urging customers to change their passwords, rotate their node credentials and regenerate their platform API keys. The incident began in October, but the company has only now published its findings.

From the Development Environment to Production

According to the company, the attacker gained access to its development environment on October 26 through a third-party vendor component. Three days later, the attacker reached part of the production environment. Chainstack detected the intrusion on October 31 and shut off the attacker’s access paths the same day.

The compromised database held customer account information, including organization names, account owners’ names, email addresses of organization members and password hashes. The company also says the attacker accessed systems that store node authentication credentials. Chainstack has found no evidence that those credentials were read, but recommends treating them as exposed.

Chainstack says customer services ran normally throughout and that nodes, the console and the API were not modified. However, no service disruption does not mean data confidentiality was preserved. Service availability and the security of the data stored in that service have to be assessed separately.

How to Limit the Impact

Customers should follow the recommendations in the company’s notice:

  • Change your Chainstack password, along with the password for any other service where you reused it.
  • Rotate your node credentials using the option available in the console.
  • Generate new platform API keys and update every integration that relies on them.
  • Be wary of messages that refer to the incident. The company stresses that it never asks for passwords, tokens or keys.

Within your organization, assign an owner to each integration being updated and confirm that the old credentials have been revoked. Creating a new key shouldn’t be the end of the process if the old one still grants access to the service.

SecurHUB Commentary

The attacker’s move from the development environment into production shows why separating privileges and controlling secrets matters. Security audits help assess these dependencies and verify that your key rotation procedures cover every integration.

Sources: Chainstack, The Hacker News

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk