WorkOS and Chainstack both disclosed on November 3 that attackers had broken into their systems, and WorkOS says the intruder used the ARTEX AI penetration-testing framework. The two incidents exposed sales contact records, customer account details and password hashes.
How the Attacker Reached the WorkOS Internal Sales Application
WorkOS, a developer identity platform with more than 3,000 customers, said it found unauthorized access to an internal application used by its sales team on October 30. The attacker reached business contact records and summaries of customer communications. The company says no production services or customer application data were touched.
Founder Michael Grinich said the attacker used the ARTEX AI penetration-testing framework. WorkOS identified the tool from two user agents that appeared in web requests: “artex-enrich/1.0” and “norma/0.4”. Grinich described the incident as contained, and WorkOS has hired an independent forensics firm to examine what happened.
WorkOS Locks Down the Sales App and Promises a Fuller Report
WorkOS disabled external access to the affected application and reviewed access controls across its internal tools. The company said it will notify affected parties and publish a fuller report once the forensic work is finished. It has not yet said how many contact records were involved.
Chainstack Intrusion Began in a Development Environment
Chainstack, a blockchain node infrastructure provider, said an external attacker entered a development environment on October 26 through a third-party component, then escalated into parts of its production systems. The company detected the intrusion on October 31 and cut off access the same day, leaving a gap of roughly five days between the first entry and detection.
Chainstack Exposed Database and Node Credential Risk
The database the attacker reached held organization names, account holder names, member email addresses and password hashes. Systems that hold node credentials were also accessible to the intruder. Chainstack says it has no evidence those credentials were read, but it tells customers to treat them as exposed.
The company advises customers to rotate node credentials and platform API keys, change their passwords, including any reused on other services, and stay alert for phishing messages that draw on the exposed account details.
ARTEX Origins and the Reported China-Linked Campaign Overlap
ARTEX began as an open-source project released by Chinese developers. It later went private after attacks on South Korean banks, though forks of the code remain public. Security reporting on the Chainstack incident says it overlaps with a campaign run by a China-linked cluster that uses ARTEX.
CrowdStrike earlier tied the group it tracks as Vapor Panda to a global ARTEX campaign against about 200 organizations. Neither WorkOS nor Chainstack has attributed its own incident to a named group, and the user agents WorkOS cited show only that the framework was in use, not who operated it.
Chainalysis Reports a Similar Agentic Intrusion
Blockchain analytics firm Chainalysis said last week that an external actor using what it called “offensive agentic techniques” accessed its systems. As of November 2 the company had taken its Reactor and Data Solutions products offline. Chainalysis has not tied that incident to ARTEX, so it is useful context rather than a confirmed link to the WorkOS and Chainstack cases.
What the Two Disclosures Show About AI-Driven Intrusion Tooling
The two incidents differ in depth. At WorkOS the attacker stayed in an internal sales system and, by the company’s account, never reached production. At Chainstack the intruder moved from a development environment into production and into a database of customer account data. Both victims sell infrastructure that other developers build on, which raises the stakes of any exposure of customer contacts or credentials.
The ARTEX user agents are an unusual detail. Automated frameworks often leave consistent request signatures, and WorkOS used those strings to name the tool behind the intrusion. Defenders who log user-agent values for internal applications can search for the same strings, although a renamed fork would not carry them.
The open questions are concrete. WorkOS has not said when its forensics firm will report, and Chainstack has not said whether any node credentials were actually read. Customers of both companies are left acting on precautionary guidance until those answers arrive.
