Black October” for AI Developer Platforms | Wiz Blog

Black October disclosed that a credential was leaked, exposing a trust relationship that could have been abused.

At least nine AI Developer Platforms have disclosed incidents over the course of the month: 11-02, 17:00 UTC - Two further incidents are publicly reported: Brev (NVIDIA) (Oct 4-20), and Trigger.dev (Nov 1).

11-03, 15:40 UTC - An further incident is publicly reported: Chainstack (October 29-31).

11-06, 17:15 UTC - kernel.sh disclosed an incident on 11-04 (Oct 24-Nov 3).

Wiz customers can refer to our relevant Threat Intel Center advisories for more information on the Railway Platform Breach, Lightning AI Security Incident and the overall campaign.

Fireworks, OpenCode, and Warp have all reported indications of an agent swarm attack.

Anyone connected to Black October through the compromised trust relationship is potentially affected, not just Black October itself.

This kind of compromise doesn't stay contained to one company; it travels to everyone who installed the affected package or image, often without any direct relationship to the original leak.

While there is no single vulnerability or dependency linking these attacks, the overall picture is strongly aligned with recent reports on two fronts: Agentic Attacks, which can enable threat actors to compromise victims faster and more efficiently.

A leaked key doesn't need an exploit to be dangerous -- it just needs to still work before someone notices and revokes it.

Fireworks, Zeabur, and Lightning all attribute their incident root causes to credential access.

Lightning was previously impacted by a supply chain attack within the Mini-Shai Hulud campaign.

The trust mechanism involved here is an API or master key, which is what let access move between otherwise unrelated systems.

OpenCode and CommandCode have explicitly attributed their incidents to an attempt at

Black October says the credential has been revoked, and no exploitation has been confirmed so far.

This indicates a single ongoing verification job checking that the keys remained valid.

Early the next morning, a checker on a shared VPN exit identified the working us.* model IDs.

If you have any integration or dependency involving Black October, rotate any credentials shared with it as a precaution, even without confirmation you were directly affected.

Whether you installed any package, image, or update from the affected registry during the exposure window is worth checking, since the compromise travels through the artifact, not just the original leak.

Your own credential inventory is worth auditing for keys or tokens with broader access than they actually need -- the same blast-radius problem applies to anything your own organization leaks.