WorkOS, Northflank, Trigger.dev disclose hacks, SecurityWeek reports

What happened

According to SecurityWeek, AI developer platforms have been hit in a wave of attacks over the past month, and the outlet says at least a dozen were affected. SecurityWeek reports that the most recent incidents involved CommandCode, Northflank, Trigger.dev, Chainstack and WorkOS. SecurityWeek also names Andromeda, Brev (NVIDIA), Fireworks AI, Lightning AI, OpenCode, Railway, Warp and Zeabur as targets, mainly for stored customer secrets. These claims come from SecurityWeek’s report, and the source does not independently verify each incident.

SecurityWeek says the hackers appear to have been hunting for AI access tokens they could monetize, and that they used AI agents to speed up their attacks. It also says the incidents do not appear to be related to one another. Initial access reportedly varies from compromised credentials to third-party dependencies and vulnerability exploitation.

Per SecurityWeek, Wiz attributes the surge to LLM-jacking and LLM broker infrastructure, which make stolen tokens easy to monetize. Wiz says it saw multiple threat actors using the same compromised keys, and two cases where the first unauthorized activity came within 30 minutes of the reported credential access in the vendor breach. SecurityWeek also quotes the Cloud Security Alliance, which says a single intrusion at a hosting layer can expose keys for many inference accounts at once.

SecurityWeek says Chainstack and WorkOS disclosed attacks this week that used the open source AI penetration testing framework Artex for automation. It adds that multiple companies have linked attacks attributed to the Chinese APT Storm-0940 to Artex, including a campaign against ConnectWise customers. The source does not attribute the Chainstack or WorkOS incidents to Storm-0940.

• Chainstack: SecurityWeek reports the company was hit on October 26 and that attackers accessed a development environment and parts of production through a third-party component. The company said a database of customer account information was accessed. Information that may have been exposed includes organization names, account holder names, member email addresses and password hashes. Node credentials might also have been exposed, and Chainstack prompted customers to rotate them.
• WorkOS: SecurityWeek says WorkOS states that on October 30 attackers compromised an internal application used by its sales team. They reportedly accessed business contact details and summaries of customer communications, including names, email addresses, phone numbers, job titles, company affiliations, account histories, sales details and information about customers’ use of WorkOS products.

Not confirmed in the source: the entry point for most of the named platforms, the amount of data taken, whether specific customer keys at Northflank or Trigger.dev were abused, and any fix or patch.

Am I affected?

The source does not give per-customer impact. You may be in scope if you:

• use any of the named platforms (CommandCode, Northflank, Trigger.dev, Chainstack, WorkOS, or the others listed above), or
• keep AI provider credentials, such as inference API keys, inside hosting platforms, evaluation services or developer consoles.

Chainstack customers should read the company’s notice. SecurityWeek says it covers possible exposure of account details, password hashes and node credentials. WorkOS customers should read the company’s notice about its sales application. According to SecurityWeek, WorkOS says the exposed data was business contact and communication information.

What to do now

1. Check your vendors’ own security notices for the platforms you use. This advisory relies on SecurityWeek’s summary, and no vendor notice was available to us.
2. If you use Chainstack, rotate node credentials, which the company has asked customers to do according to SecurityWeek.
3. As a precaution, consider rotating AI provider keys and other secrets stored on any affected platform. SecurityWeek says stolen keys were reportedly reused by multiple actors, but it does not give this as a vendor instruction.
4. If you use Chainstack, treat password hashes as possibly exposed, as the company says they may have been, and change account passwords.
5. Review usage logs on your AI provider accounts for activity you do not recognize. This is our suggestion, not one from the source.

Sources

• SecurityWeek: AI-Linked Breaches Mount as WorkOS, Northflank, Trigger.dev Disclose Hacks