Chainstack said an attacker queried a production database after entering through a test environment, leaving some customer names, email addresses and password hashes potentially exposed.
In its Nov. 10 incident update, Chainstack said its review found queries to an account database and warned that information there may have been exposed.
Chainstack traced the entry to a Grafana test installation whose default administrator password remained in place. The intruder used Grafana’s proxy to connect to internal services, including an unauthenticated MCP server with Kubernetes cluster-admin rights in development. Machine identities obtained later enabled access to parts of production, while a VPN key provided a route to the database network.
Chainstack dated the initial access to Oct. 26 and said the attacker reached parts of production on Oct. 29. It said it blocked the access routes on Oct. 31 and finished its investigation Nov. 2.
The account database included names for organizations and account holders, along with members’ email addresses and password hashes, Chainstack said. The company said those details may have been exposed; it found no evidence node credentials were read but is treating them as exposed because the attacker reached systems storing them.
Chainstack asked customers to reset passwords and replace node credentials. It directed customers who use the platform API to issue fresh API keys. The company said customer services continued without interruption and its review found no alterations to customer nodes, the console or the API.
Chainstack found no indication that the attacker exploited a software vulnerability. The company assessed with high confidence that ARTEX, an open-source framework for coordinating language-model agents, was used. It said that conclusion concerns the attack software and does not reveal who operated it.
