Cloud roundup: 153GB LiteLLM breach exposes cloud secrets

The big story today isn’t a new breach — it’s the bill coming due on an old one. A researcher got hold of the actual haul from March’s LiteLLM supply-chain attack, and the scale is worse than the original disclosure suggested. On the AWS side, two changes worth planning around: more control over your EKS control plane, and a pricing shift that quietly doubles some OpenSearch costs.

153GB of stolen credentials surface from the March LiteLLM attack

Back in March, attackers compromised the Trivy scanner and used it to slip two malicious versions of LiteLLM onto PyPI for about 40 minutes — long enough for a .pth file to start harvesting secrets from every CI run that installed it. Hudson Rock has now obtained and analyzed the actual stolen archive: 153GB, 433,909 files, with 118,829 CI runner dumps attributable to 2,488 corporate domains — including AWS, Cisco, Samsung, Salesforce, Microsoft, and dozens of other large enterprises (Help Net Security). The dumps include AWS secret access keys, Salesforce client secrets, Slack signing secrets, and Azure environment variables captured mid-pipeline. The uncomfortable part: any credential that was live in a CI runner during that 40-minute window is still valid until someone actively rotates it — removing the malicious package did nothing to invalidate what it already stole. If you had LiteLLM anywhere in a CI/CD dependency tree back in March, this is worth a credential audit today, not a “we’ll get to it” item — check for AWS keys, Slack tokens, and cloud provider secrets that predate March 19 and haven’t been rotated since.

Amazon EKS now lets you tune scheduler, controller manager, and API server parameters

AWS added support for configuring Kubernetes control plane parameters directly on EKS — scheduler behavior, controller-manager settings, and API server options that used to require self-managing the control plane to touch (AWS). The scheduler example AWS calls out is a good one: switching the node resource fit strategy from the default LeastAllocated (spread pods across nodes) to MostAllocated (pack nodes tightly) can meaningfully cut node count for workloads where you don’t need the spare headroom. It’s available in every region EKS runs in, no migration required. Worth a look if you’ve ever wanted more control over pod-placement or autoscaling responsiveness on EKS without giving up the managed control plane.

OpenSearch/Elasticsearch Extended Support surcharge is about to double

AWS extended the security-patch window for older Elasticsearch (1.5–7.8) and OpenSearch (1.0–1.2, 2.3–2.9) versions through November 7, 2027 — but from November 7, 2026, the Extended Support surcharge jumps to equal your instance cost, effectively doubling the price of running those old versions (AWS). If you’ve got domains sitting on a pre-7.9 Elasticsearch or early-2.x OpenSearch version because upgrading was never urgent, this is the forcing function: budget for either the upgrade or the doubled bill before November.

Bottom line

The LiteLLM fallout is the one to act on today — a credential rotation check costs you an hour and closes a door that’s been open since March. The AWS items are both “plan now, act before the deadline” — EKS control plane tuning whenever you get to it, OpenSearch versions before the November surcharge hits.