TrapDoor Supply Chain Attack Distributes Credential-Stealing Malware Across Ecosystems
Audit all packages for TrapDoor malware and remove infected ones.
Run package integrity checks and remove any TrapDoor packages.
Summary
A coordinated cross-ecosystem supply chain attack, codenamed TrapDoor, has targeted npm, PyPI, and Crates.io to distribute credential-stealing malware. The campaign spans more than 34 malicious packages across over 384 versions, with the earliest activity recorded on May 22, 2026. Attackers publish infected packages in waves from a cluster of compromised accounts, exploiting the trust model of open-source ecosystems. The malware harvests credentials from the victim’s environment and exfiltrates them to remote servers.
Security researchers recommend auditing all dependencies for TrapDoor signatures and removing any infected packages. The attack demonstrates the need for integrity checks and automated scanning of third-party libraries. Package maintainers should verify the authenticity of their releases and monitor for suspicious activity. Organizations should implement strict package provenance policies to mitigate future supply chain threats.
Key changes
- TrapDoor campaign targets npm, PyPI, Crates.io with credential-stealing malware
- 34 malicious packages across 384+ versions, first activity May 22, 2026
- Attackers publish infected packages in waves from compromised accounts
- Malware harvests credentials and exfiltrates them to remote servers
- Researchers recommend auditing dependencies and removing infected packages