CuraSec

tag: Pypi · 2 items

Act LiteLLM PyPI and Docker images backdoored with credential-stealer
2026-10-23 · BleepingComputer · source ↗ #supply-chain#malware#pypi
  • Engineer — Act: LiteLLM is a widely adopted Python LLM gateway library; compromised PyPI releases and Docker images can steal env vars, API keys, and secrets from any pipeline that installs or pulls them. Audit all CI/CD and container builds for LiteLLM usage, pin or remove affected versions immediately, and rotate any credentials that ran in affected environments.
  • SOC/IR — Act: Active supply-chain malware distributing an info-stealer via a popular AI library is an assume-breach scenario for any org using LiteLLM in their stack. Hunt for anomalous outbound connections from build agents and containers, and sweep secrets-management logs for unexpected access since the compromise window.
  • Leader — Act: A compromised open-source AI library used heavily in LLM integration work creates real credential-exposure risk across engineering teams. Confirm whether LiteLLM appears in any internal projects, direct teams to audit and remediate this week, and assess whether any cloud or SaaS credentials were potentially stolen.
Act archived Malicious LiteLLM PyPI Releases Stole Cloud/K8s Creds from 2,100+ Orgs
2026-08-12 · The Hacker News · source ↗ #supply-chain#pypi#credential-theft
  • Engineer — Act: If LiteLLM was installed in any environment during March 2026, assume cloud keys, SSH keys, and Kubernetes tokens from that system were exfiltrated — rotate all credentials from affected hosts and audit CI/CD pipeline logs for installs during that window.
  • SOC/IR — Act: Hunt for anomalous cloud API activity and Kubernetes token usage dating back to March 2026 on any host where LiteLLM was installed; CloudSEK’s 434,000-file dataset suggests usable IOC context is emerging, so watch for actor TTPs tied to the Trivy campaign.
  • Leader — Act: Confirm with engineering whether LiteLLM or Trivy are in use in the AI/ML stack; if so, direct a credential-rotation audit this week and assess whether any customer data environments were reachable from affected systems — 2,100+ exposed organizations makes this a peer-company disclosure risk worth tracking.