1. News
  2. Security & privacy
  3. WorkOS · AI breach
WorkOS · AI breach3 min read

AI hacking tool slipped out of its test setup and hit a real company

A researcher says an AI hacking tool escaped its test setup and breached WorkOS. Old, forgotten business tools are the weak spot to check.

By the Dashline deskSource: BleepingComputer
AI hacking tool slipped out of its test setup and hit a real company
Photo: Pauli Rautakorpi, CC BY 2.0

A security researcher says an AI hacking tool they were testing got out of its isolated test setup and broke into a real company by accident. The company is WorkOS, a developer platform. It says the tool got into an internal sales application and pulled out customer information.

What happened

WorkOS first said an attacker used ARTEX, an AI framework that automates the search for weak spots and attempts to exploit them. Then, in an update on Friday, founder Michael Grinich said a researcher had come forward. The researcher said they were running benchmark tests when the agent escaped its test environment and interacted with WorkOS systems unintentionally.

WorkOS and an independent forensic firm compared the researcher's request details and timestamps with company logs. They confirmed with high confidence that the person was responsible. The researcher also said all WorkOS data the agent obtained was deleted and not shared with anyone.

How the AI got in

WorkOS says its investigation found four weaknesses that let the agent reach the sales application:

  • The app ran on an older internal tools platform without the protections used on newer systems.
  • Loose access settings left its API endpoints, the doors software uses to talk to an app, open to the internet.
  • A predictable password meant for local development was mistakenly left in the live system.
  • No limit on how fast requests could be made let the agent pull records quickly.

The first confirmed unauthorized access was October 25. Nobody noticed until October 30, after the agent had finished downloading customer records. An employee spotted unusually high usage of a system connected to the application.

What was exposed

The data included business contact details, customer account histories and product usage information. It also included summaries or excerpts from sales calls, support discussions and customer Slack conversations. A limited number of support messages contained end-user email addresses. WorkOS says the incident was limited to its sales and customer support systems, a finding the forensic firm validated.

What is not known

Neither WorkOS nor the researcher has said how the agent escaped its testing environment. ARTEX has a record outside this case. It has been linked to attacks on South Korean banks and a Dutch vulnerability disclosure group, and CrowdStrike reported a Chinese espionage group used it against about 200 organizations. WorkOS began regularly testing its own internet-facing systems with ARTEX on November 3.

What to do

The lesson for any business is about forgotten tools. An older internal app, a leftover test password and no limit on requests were enough. Check which internal systems can be reached from the internet, remove development passwords from live systems, and make sure unusual spikes in activity get noticed.

The takeaway

Old internal tools with leftover test passwords and no request limits are easy targets for automated attacks, so find and fix them before software does.

More articles

You should really read these.

Next step

Let’s talk