WorkOS says an AI-assisted attack framework reached its internal sales tool and CRM data
WorkOS found unauthorized access on October 30 to an internal tool its sales and customer teams use, exposing CRM contacts, call and Slack excerpts, and directory health metadata. It saw an AI-assisted offensive framework and no access to production or application data.
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 and conditional access policy as production. Similar cases are in our breach incident database.
Source: WorkOS security bulletin
Related on Start with Identity
- BlogChainstack says an attacker reached production through a third-party component and took password hashes
Blockchain infrastructure provider Chainstack says an attacker entered a development environment through a third-party component on October 26, reached producti
- BlogDigiCert says self-registered accounts read archived customer data, including some ID documents
DigiCert is notifying customers that an unauthorized, self-registered account read archived customer records from an internal business system between June 27 an
- BlogBinance says a fake job interview and an internal AI tool led attackers to its wallet signing service
Binance's initial findings trace the $6.34 billion theft to a September fake recruiter whose coding assignment infected an engineer's Mac. An internal AI tool l
- CVEJFrog Artifactory hands its internal anonymous-user token to unauthenticated callers
Self-hosted Artifactory could return an internal anonymous-user token to an unauthenticated request even with anonymous access disabled. Attackers chained it wi
- GlossaryAttack Path
A chain of individually legitimate permissions and relationships that together let a low-privileged identity reach a high-privileged one. Each link is a valid c
- Comparisonauth0-vs-workos
Auth0 is a complete developer-first CIAM platform for B2C and B2B login. WorkOS is the enterprise-readiness layer (SAML SSO, SCIM directory sync, audit logs) fo