BotBeat
...
← Back

> ▌

Python Software Foundation / PyPIPython Software Foundation / PyPI
POLICY & REGULATIONPython Software Foundation / PyPI2026-04-03

PyPI Addresses Supply Chain Attacks on LiteLLM and Telnyx; Malware Injected Into Widely-Used Packages

Key Takeaways

  • ▸Supply chain attacks are evolving to inject malware into established, widely-used packages rather than publishing new malicious packages, targeting valuable API credentials
  • ▸LiteLLM and Telnyx packages were compromised with credential-harvesting malware that executed on install and exfiltrated sensitive data to remote servers
  • ▸PyPI's rapid response (2-4 hours quarantine time) was enabled by community security researchers and automated quarantine systems triggered by trusted reporters
Source:
Hacker Newshttps://blog.pypi.org/posts/2026-04-02-incident-report-litellm-telnyx-supply-chain-attack/↗

Summary

Popular Python packages LiteLLM and Telnyx were compromised in recent supply chain attacks where malware was injected directly into widely-used open source projects after credential exposure. The malware harvested sensitive credentials and files during installation and exfiltrated them to remote servers. LiteLLM's compromised versions were downloaded over 119,000 times, with approximately 40-50% of typical weekly installs pulling the malicious latest version before quarantine. PyPI's security response quarantined the LiteLLM malware within 2 hours 32 minutes and the Telnyx malware within 3 hours 42 minutes of upload, leveraging community reports and an automated quarantine system powered by trusted security reporters. The incident represents a new class of supply chain threat distinct from typical PyPI malware, which targets established projects with valuable API tokens rather than publishing new typosquatted packages. PyPI is collaborating with affected maintainers on remediation including token rotation, release removals, and adoption of security best practices like Trusted Publishers.

  • Developers are advised to implement 'dependency cooldowns' to allow time for malware detection and remediation on frequently-updated packages
  • Both affected projects have now adopted Trusted Publishers and other enhanced security practices to prevent future compromise

Editorial Opinion

This incident underscores a critical vulnerability in the open source supply chain: the tension between rapid dependency updates and security vetting. While PyPI's response time of 2-3 hours is commendable, the fact that malicious versions reached tens of thousands of installations highlights the asymmetric nature of software security—attackers need only one successful compromise, while defenders must catch every threat. The shift toward injecting malware into trusted packages rather than creating new malicious ones is particularly concerning and suggests attackers are increasingly targeting the ecosystem's most critical leverage points.

MLOps & InfrastructureCybersecurityPrivacy & Data

Comments

Suggested

Google / AlphabetGoogle / Alphabet
RESEARCH

Deep Dive: Optimizing Sharded Matrix Multiplication on TPU with Pallas

2026-04-05
PerplexityPerplexity
POLICY & REGULATION

Perplexity's 'Incognito Mode' Called a 'Sham' in Class Action Lawsuit Over Data Sharing with Google and Meta

2026-04-05
SourceHutSourceHut
INDUSTRY REPORT

SourceHut's Git Service Disrupted by LLM Crawler Botnets

2026-04-05
← Back to news
© 2026 BotBeat
AboutPrivacy PolicyTerms of ServiceContact Us