--- title: "Inside the LiteLLM Hack: 153GB and 2,488 Organizations" url: https://daily.dev/posts/inside-the-litellm-hack-153gb-and-2-488-organizations-o6bjdggod source_url: https://blog.gitguardian.com/inside-the-litellm-hack type: article source: "GitGuardian" published: 2026-08-14T18:24:47.644Z updated: 2026-08-14T18:25:58.627Z tags: ["cyber", "python", "cicd", "secrets-management"] reading_time: 4 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Inside the LiteLLM Hack: 153GB and 2,488 Organizations **[GitGuardian](https://daily.dev/sources/gitguardian)** · 4 min read · 0 upvotes · 0 comments ## Summary Hudson Rock and CloudSEK published new analyses of the loot from the March LiteLLM PyPI supply chain compromise, revealing a 153GB RAR archive with 433,909 files. The attacker's infostealer ran during a 40-minute window on compromised CI runners, escalating to root and harvesting SSH keys, AWS/GCP/Azure credentials, Kubernetes tokens, .env files, LLM API keys, and gateway configs. Researchers attributed 118,829 CI runner dumps to 2,488 corporate domains, including a case where a SiriusXM committer email pointed to AdsWizz infrastructure, showing attribution by email alone can misroute alerts. A significant, unquantified portion of dumps carry live credentials with no identifiable company domain, meaning those organizations cannot be notified through responsible disclosure. The piece argues detection must happen internally via non-human identity inventories, endpoint secrets scanning, continuous validity checks, and honeytokens, since the malware ran on developer laptops as well as CI runners and never touched a repository. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How many organizations were affected by the LiteLLM supply chain attack that happened in March? Hudson Rock's analysis of the 153GB exfiltration archive attributed 118,829 CI runner dumps to 2,488 corporate domains. The archive contained 433,909 files total, collected during a roughly 40-minute window in which malware embedded in litellm PyPI builds escalated to root on CI runners and developer machines, harvesting SSH keys, cloud credentials, Kubernetes tokens, and LLM API keys. _Teams tracking supply chain fallout can follow breach analyses like this one on daily.dev._ ### What kind of credentials did the LiteLLM PyPI malware steal from CI runners? The malware harvested SSH keys, AWS/GCP/Azure credentials, Kubernetes service account tokens, .env files, and general CI/CD secrets after escalating to root on compromised runners. On AI-related builds it additionally stole LLM API keys and gateway configuration, giving attackers access to an organization's entire model stack rather than a single credential. One organization had 17 dumps exposing Bitbucket tokens, Elastic API keys, internal JWTs, and NPM tokens. _Developers securing CI pipelines can track incident writeups like this on daily.dev when auditing secrets exposure._ ### Why can't every company affected by a data breach be notified about it? Many dumps in the LiteLLM breach archive contain live database passwords, cloud credentials, and API keys with no company email, custom domain, or internal hostname attached, making them impossible to attribute to a specific organization. Neither Hudson Rock's ethical disclosure program nor CloudSEK's public lookup tool can notify a victim they cannot identify, leaving those organizations off any disclosure list. _daily.dev helps security teams stay current on breach research so unattributed exposure risks don't go unnoticed._ --- Tags: [#cyber](https://daily.dev/tags/cyber), [#python](https://daily.dev/tags/python), [#cicd](https://daily.dev/tags/cicd), [#secrets-management](https://daily.dev/tags/secrets-management) [View this post on daily.dev](https://daily.dev/posts/inside-the-litellm-hack-153gb-and-2-488-organizations-o6bjdggod)