# WorkOS says an AI-assisted attack framework reached its internal sales tool and CRM data

Source: https://startwithidentity.com/blog/2026-11-02-workos-says-ai-assisted-attack-reached-internal-sales-tool-and-crm-data/
Last updated: 2026-11-02
License: content by Start with Identity. Cite the source URL.

---

[WorkOS](https://startwithidentity.com/vendors/ciam/workos/), which sells enterprise SSO, directory sync and user management APIs to software companies, disclosed that on October 30 it found unauthorized access to an internal application used by its sales and customer-facing teams. Exposed data includes CRM contact details (names, emails, phone numbers, job titles and companies), account histories, summaries and excerpts of sales calls, support discussions and customer Slack conversations, and operational metadata such as product usage and connection or directory health. WorkOS says its investigation found "the use of an AI-assisted offensive security framework to automate reconnaissance and exploitation attempts," and no evidence that WorkOS application data or production services were accessed. It disabled external access to the tool, hired an outside forensics firm and will contact affected customers. BleepingComputer, citing WorkOS's Michael Grinich, reported request user agents such as `artex-enrich/1.0`, pointing to the ARTEX AI framework.

## Why it matters

Connection and directory health metadata tell an attacker which customers run which identity provider and where an SSO or SCIM integration is failing, which is the raw material for a convincing support pretext. WorkOS tells customers to verify unexpected requests "even when a message references a real colleague or support conversation." Sales and support tools are rarely held to production access standards, yet they now hold call transcripts and Slack excerpts.

If you are a WorkOS customer, treat any message about your SSO or directory connection that asks for a change, a credential or a call as suspect until you verify it through a known channel. For your own stack, put internal sales and support apps behind the same [SSO](https://startwithidentity.com/glossary/sso/) and [conditional access](https://startwithidentity.com/glossary/conditional-access/) policy as production. Similar cases are in our [breach incident database](https://startwithidentity.com/breaches/incidents/).

Source: [WorkOS security bulletin](https://workos.com/security/bulletins/october-30th-2026-data-security-incident)