Poisoned Pipeline / Incidents / AS344
A third-party component led an attacker into Chainstack's development and production systems
On 3 November 2026 Chainstack published an incident report for an
intrusion it had detected three days earlier. The report says an
external attacker gained unauthorised access to part of Chainstack's
infrastructure through a third-party component, and places the
incident inside the broader campaign against AI and developer
platforms that was reported in late October. Chainstack does not name
the component, and it does not say whether the actor is the same one
behind the other October platform breaches.
The timeline the report gives, all in 2026: on 26 October the
attacker gained access to a development environment; on 29 October to
parts of the production environment; on 31 October Chainstack
detected the intrusion and cut the access paths the same day; on
2 November it closed the investigation. Customer-facing services
continued to operate, and the company says customer nodes, the
console and the API were not modified. It does not store full card
numbers or security codes, so those were not exposed.
What the attacker reached was a database holding customer account
information - organisation names, account holder names, the email
addresses of each organisation's members and password hashes - plus
systems holding node credentials. Chainstack says it has no evidence
the node credentials were read, and is treating them as exposed
anyway. Every customer was notified by email and asked to change
passwords, including anywhere they were reused, rotate node
credentials through the console's self-service rotation, regenerate
platform API keys, and watch for phishing. The report gives no
customer count and no evidence of the credential use that would show
what the actor did next.
Mapped techniques
- T0180 Compromise services / servers
- T0184 Harvesting sensitive information from files
- T0199 Secret leak
- T0201 Customers compromised
supply-chain Chainstack infrastructure
The attacker reached a Chainstack development environment on
26 October and parts of production on 29 October, and was
detected on 31 October. Entry was through a third-party
component in the provider's own infrastructure, which the
report does not name.
The attacker reached a database of customer account records
and the systems holding node credentials. Chainstack says
there is no evidence the node credentials were read and
treats them as exposed regardless.
post-supply-chain Customer accounts and nodes on Chainstack
Account holder names, member email addresses and password
hashes were in the accessed database, and node credentials sat
on reachable systems. Chainstack asks every customer to change
passwords and rotate node credentials rather than only those
it can prove were read.
The exposure does not stop at the provider: customers run
nodes with the credentials Chainstack holds, so rotation is
required in their environments and not only in the vendor's.
Framework gaps noted
- The third-party component that gave access is not named and no CVE or vendor advisory is cited, so the entry point is not mapped as a vulnerable product.
- Chainstack links the intrusion to the late-October campaign against AI and developer platforms but does not name the actor or confirm it is the same one. Not merged with the Railway, Zeabur or OpenCode stories.
- Whether the node credentials were read, how many customers were affected, and whether the password hashes were cracked are all unpublished.