WorkOS says an AI-assisted attack reached its sales tool, with customer contacts and Slack excerpts

WorkOS sells the sign-in plumbing behind a lot of business software: single sign-on, directory sync and login pages that other companies build into their apps. On November 2, 2026, it published a security bulletin saying someone got into an internal tool its sales and customer-facing teams use. What was in reach is business information about WorkOS customers, not the logins of the people who use those customers’ apps. If your company is a WorkOS customer, here’s what it has said and what to do.

What happened

WorkOS says it identified unauthorized access to an internal application used by its sales team on October 30. Its investigation “identified the use of an AI-assisted offensive security framework to automate reconnaissance and exploitation attempts.” The bulletin doesn’t name the tool. Founder and chief executive Michael Grinich said in a post on X that the attack involved ARTEX, an open-source framework that uses AI agents to carry out attacks, Runtime Wire and Cyber Security News report.

WorkOS says it disabled outside access to the application, hired an independent digital forensics and incident response firm, and is reviewing access controls on its other internal tools. It hasn’t said how the attacker reached the application.

What was in reach

The bulletin lists four kinds of information the affected application gave access to:

• Business contact details: names, email addresses, phone numbers, job titles and company affiliations from WorkOS’s customer relationship management (CRM) systems
• Account and relationship information: customer account histories and sales and relationship notes
• Customer communications: summaries and excerpts from sales calls, support discussions and customer Slack conversations
• Operational metadata: how customers use WorkOS products, including usage and the health of their connections and directories

WorkOS is careful to say these are the categories the tool could reach, and that it is still reviewing which records were affected for each organization. It says there is no evidence that WorkOS application data was accessed, and no evidence that its production services were accessed or affected. Its current analysis is that only CRM and customer support data was involved. It will contact affected customers directly.

Why it matters

The people in these records are mostly engineers, security staff and buyers at companies that use WorkOS. What makes the data sensitive is the conversations. An attacker who has read your real support thread or a summary of your sales call can write a message that sounds exactly like the follow-up you were expecting. WorkOS makes that point itself: “Even when a message references a real colleague or support conversation, verify unexpected requests before sharing sensitive information or taking action.”

It also isn’t the only recent disclosure to describe AI-driven attack tooling. Microsoft said on October 21 that a China-aligned group used ARTEX to automate its campaign against ConnectWise’s Microsoft 365 backup app. On October 30, Chainalysis said an outsider used “offensive agentic techniques” to reach its internal tools and see customer names and emails. Neither WorkOS nor any researcher has said the same people are behind these incidents. The common thread is that automation lets attackers probe many internal tools quickly, and sales and support systems often have weaker controls than production.

If your company uses WorkOS

1. Watch for WorkOS’s own message with the findings for your organization. Don’t act on a lookalike: check that it comes from WorkOS through a contact you already have.
2. Treat unexpected requests that mention past WorkOS conversations with care, especially ones asking for credentials, a changed SSO or directory setting, a new admin, or an urgent call. Confirm through a channel you already use.
3. Think back over what was shared with WorkOS in Slack or support. If an API key, client secret, password or other credential was ever pasted into those conversations, rotate it. WorkOS hasn’t said any were exposed; this is just good practice now that excerpts of those chats were in reach.
4. Check your WorkOS dashboard and your identity provider for admins, connections or redirect URLs you don’t recognize. WorkOS says production wasn’t touched, so this is a quick sanity check rather than an emergency.
5. Brief the people listed as your WorkOS contacts (often engineering, IT and security leads) so they know to expect convincing follow-up phishing.

If you just use an app that signs in with WorkOS

There’s nothing to change. WorkOS says the affected tool held its own business records about its customers, and that it has found no evidence that application data, the data about you as an end user, was accessed.

How Frame helps

Add this breach to a verified email in Frame and Frame shows what it exposed, gives you a short checklist and counts it in your exposure report. Frame can also look up your verified emails in Have I Been Pwned’s breach database. Frame’s email aliases also let you give each vendor its own address, so a leak at one doesn’t reach everything. Frame never collects or stores the leaked records themselves.

Related coverage

• Chainalysis says an intruder reached its internal tools: another company that disclosed agent-driven access to internal systems the same week.
• ConnectWise’s Microsoft 365 backup app: the campaign Microsoft says used ARTEX to automate its attacks.

Sources

• WorkOS, October 30th, 2026 Data Security Incident, November 2, 2026
• Runtime Wire, WorkOS says ARTEX attack accessed internal sales tool, November 2, 2026
• Cyber Security News, Hackers Use ARTEX AI to Breach WorkOS and Access Customer Slack Conversations, November 3, 2026
• Microsoft Threat Intelligence, AI-driven, large-scale nation-state campaign using ARTEX enables supply chain compromise, October 21, 2026