Chainstack Discloses Breach Exposing Customer Account Data
The company says attackers entered through an exposed Grafana instance in a development Kubernetes cluster and urges customers to rotate credentials.
Updated on Nov. 12, 2026 in Cybersecurity

Live Poll
Do you trust crypto companies to keep your account data safe?
Chainstack disclosed a security breach that exposed customer account data, though its customer nodes, console and API were not modified. The attacker entered through an internet-exposed Grafana instance whose default administrator credentials had not been changed.
Why it matters
The incident shows how default credentials, missing authentication and excessive permissions can chain together to reach production systems. Customers who use Chainstack's services may need to take action to protect their accounts and node access.
The company's timeline spans from October 26, when the attacker first accessed the exposed Grafana instance, to November 2, when a copied credential was last used. Chainstack has not stated whether any copied credentials were used beyond that date, and the full scope of exposed account data remains under review.
The players
Chainstack
Chainstack is a blockchain infrastructure company that provides node and API services to developers and enterprises.
The details
The attacker reached an unauthenticated MCP server with cluster-admin privileges through Grafana's data-source proxy. Chainstack assessed with high confidence that the attacker used ARTEX, an open-source framework that orchestrates LLM agents, and found no exploited software vulnerability.
Timeline
October 26: Attacker first accessed the exposed Grafana instance.
October 29: Attacker gained production access.
October 31: Chainstack detected the intrusion and cut access paths.
November 2: Chainstack observed last use of a copied credential.
Threat Landscape
The intrusion is notable because Chainstack assessed with high confidence that the attacker used ARTEX, an open-source framework that orchestrates LLM agents, to chain together basic misconfigurations. This places the breach within a growing pattern of attackers using automated agent tools to move through systems that rely on default credentials and missing authentication.
Customers should rotate node credentials, change passwords and regenerate API keys as Chainstack recommends. Anyone who uses Chainstack's services should check whether their member email address or account details may have been affected.
The takeaway
Organizations should change default credentials and restrict unauthenticated access to internal dashboards, since the breach chained together several basic misconfigurations. Regular credential rotation limits how long a copied key remains useful to an attacker.
Further reading
For more on how attacks like this unfold, see our Cybersecurity coverage.
Live Poll
Do you trust crypto companies to keep your account data safe?



