Poisoned Pipeline / Incidents / AS345
Lightning AI took its Studio platform offline after customer credentials reached environments and connected services
AI platform / inference provider
At 23:00 UTC on 15 October 2026 Lightning AI identified a security
incident on the Lightning Platform involving unauthorised access to
credentials, and at 01:00 UTC on 16 October it revoked all user access
to the platform. The affected services are the Studio platform -
Studio, Deployments, Pipelines and Drive. The GPU cluster rental
infrastructure and the managed Kubernetes and SLURM services were not
involved.
Lightning says certain customer credentials were compromised and used
to gain access to customer environments and to third-party services
connected to them. It revoked all identified credentials, engaged an
independent external firm, and kept the platform closed to all users
while it worked. On 28 October read-only Drive access was restored
through the CLI, with Studio, Jobs and Deployments still to follow.
Customers are told to rotate secrets, API keys and credentials stored
in AI Studios, including GitHub credentials, to update credentials for
the third-party services their virtual machines reach, to review those
providers' access logs for the incident window, and to treat the
platform's own revocation of affected keys as separate from rotating
the credentials behind them.
Lightning has not published the root cause, the number of affected
accounts or the route by which the credentials were obtained. Wiz's
30 October roundup lists Lightning among at least nine AI developer
platforms breached that month, notes that Fireworks, Zeabur and
Lightning all attribute root cause to credential access, and records
that Lightning had earlier been hit by the Mini-Shai-Hulud npm
campaign. That earlier campaign is a separate operation and is not
merged here.
Mapped techniques
supply-chain Lightning AI Studio platform
Unauthorised access to credentials on the platform reached
customer Studio environments and the third-party services
those environments could reach. The platform was closed to
all users on 16 October and stayed closed for days while the
provider investigated.
The credentials at issue are the secrets and API keys held in
AI Studios and the credentials for services the Studios'
virtual machines reach, including GitHub credentials.
post-supply-chain Customer Studio environments
Lightning revoked identified keys tied to customer cloud
accounts and told every customer to rotate secrets, API keys,
GitHub credentials and third-party service credentials, and to
check those providers' logs for use in the window.
Framework gaps noted
- The root cause and the route by which platform credentials were obtained are unpublished, so the entry point is not mapped as a vulnerable product or as phishing.
- The number of affected accounts and the identity of the actor are not stated.
- Not merged with Mini-Shai-Hulud: Lightning was a victim of that npm campaign earlier in the year, which is a different operation.