WorkOS, the developer platform that provides single sign-on, directory sync and login tools to software companies, has confirmed a data breach after an attacker gained access to an internal application used by its sales team. The company says it identified the unauthorized access on October 30, 2026, and that the intruder relied on an AI-assisted offensive security framework to automate reconnaissance and exploitation attempts.
In a security bulletin dated November 2, WorkOS said there is no evidence that WorkOS application data was accessed and no evidence that its production services were accessed or impacted. Its current analysis indicates the incident affected only CRM and customer support data.
What the attacker could reach
According to WorkOS, the affected internal application provided access to 4 categories of information:
- Business contact details: names, email addresses, phone numbers, job titles and company affiliations held in its customer relationship management (CRM) systems.
- Account and relationship information: customer account histories and sales and customer relationship details.
- Customer communications: summaries and excerpts from sales calls, support discussions and customer Slack conversations.
- Operational metadata: information about how customers use WorkOS products, including product usage and connection or directory health.
WorkOS said it is still reviewing the affected records to determine the impact on individual organizations. It has not said how many customers are affected or how the attacker first gained access to the application.
CEO says the attack involved ARTEX
The bulletin itself does not name the framework. WorkOS founder and CEO Michael Grinich did in a post on X on November 2, writing that the incident was isolated to internal go-to-market (GTM) systems and that the attack involved ARTEX, an autonomous AI agent framework used to carry out offensive security operations.
I want to share some context on a security incident we discovered on October 30.
First, the most important thing: WorkOS's production systems are secure. No customer platform data was accessed. This incident was isolated to internal GTM systems.
The attack involved ARTEX, an…
– Michael Grinich (@grinich) November 2, 2026
When asked for technical evidence, Grinich replied that WorkOS identified user agents such as artex-enrich/1.0 and norma/0.4 in web requests from the threat actor. Based on public reporting from Wiz and forks of the open-source ARTEX tool, he said those user agents are likely attributable to ARTEX. In a later reply, he added that the attacker’s behavior patterns match what others have seen and that WorkOS hopes to publish more indicators of compromise as the investigation progresses.
User agent strings are easy to change, so they point to a tool rather than a specific attacker. WorkOS has not named a threat actor.
How WorkOS is responding
WorkOS said it disabled external access to the affected application and is conducting a broader review of access controls on its internal tools. It has retained an independent digital forensics and incident response firm to establish the full scope of the activity. The company said it will contact affected customers directly and share further updates as it verifies more information.
The company also warned customers to stay alert for phishing and social engineering. Business contact details and excerpts from real conversations can help an attacker make a fraudulent request look legitimate, so WorkOS advises verifying any unexpected request before sharing sensitive information, even when a message references a real colleague or support thread.
Part of a wider wave of attacks on developer platforms
The WorkOS breach lands in the middle of a surge of incidents at developer and infrastructure companies. Wiz’s “Black October” research counted 9 AI developer platforms that disclosed incidents in October, including Northflank, which told every customer to treat stored secrets as compromised. Blockchain infrastructure provider Chainstack confirmed a breach exposing customer data and node credentials, and Chainalysis disclosed a breach after an attacker used offensive agentic techniques.
Background job platform Trigger.dev also disclosed a separate incident on November 1. In a security disclosure signed by CTO Eric Allam, the company said an attacker gained unauthorized access to environment variables for a subset of organizations, that the exploit has been blocked and that impacted account owners were emailed mitigation steps. Trigger.dev has not linked its incident to ARTEX.
ARTEX itself has been tied to several campaigns this year. CrowdStrike reported that the Vapor Panda espionage group used ARTEX AI agents against more than 200 organizations. Microsoft attributed the ConnectWise supply chain attack to Storm-0940, an actor it says has used ARTEX since as early as September, and Wiz is tracking an ARTEX-using actor overlapping with Storm-0940 across multiple software vendors. Google’s threat intelligence team has also published an analysis of ARTEX and other agentic offensive frameworks. Nothing WorkOS has published links its incident to a specific campaign or actor.
What WorkOS customers should do
- Treat unexpected emails, calls or Slack messages that cite past WorkOS sales or support conversations with caution, and confirm requests through a known channel.
- Rotate any API key, token or credential that was ever shared in a WorkOS support ticket, sales thread or shared Slack channel.
- Search web and API logs for the user agents
artex-enrich/1.0andnorma/0.4. - Customers with questions can email security@workos.com, the address Grinich shared publicly for customers who want a call with the WorkOS security team.
