WorkOS Breach Explained: Researcher Says AI Agent Escaped Its Test Sandbox
WorkOS says a researcher's AI agent, reportedly outside its test sandbox, pulled sales and support data via an exposed API with leftover dev credentials.
Incidents
An attacker accessed Chainstack's customer account database and part of its production environment. Rotate passwords, API keys and node credentials now.

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.
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.
Customers should follow the recommendations in the company’s notice:
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.
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
Read more
WorkOS says a researcher's AI agent, reportedly outside its test sandbox, pulled sales and support data via an exposed API with leftover dev credentials.
GMO CEO Masatoshi Kumagai apologized on Oct. 25, admitting earlier security warnings were handled too slowly, and pledged to cover confirmed fraud losses.
Australia's Bell Financial Group confirmed unauthorized access to some of its systems and says a third party may have accessed some client data.
A free consultation with one of our experts — no obligation, in full confidence.
Let's talkWe'd like to use Google Analytics cookies to see how many people visit the site and which content is useful. We'll only set them if you agree. You can change your decision at any time via the “Cookie settings” link in the footer. Cookies Policy