Cross-Registry Package Attack Turns Ecosystems Into Trapdoors
This is not a single bad package problem. TrapDoor spreads across npm, PyPI, and Crates.io, so the trust boundary is the package ecosystem itself, not one maintainer account or one language registry. Generic-looking developer tools in crypto, DeFi, AI, and security workflows can become credential theft points before teams realize they are under attack.
Socket says the campaign spans more than 34 malicious packages and 384+ related versions and artifacts, with activity published in waves and some packages still live at publication. The earliest sample seen was eth-security-auditor@0.1.0 on May 22, 2026, and the packages are built to steal developer secrets, crypto wallets, SSH keys, cloud credentials, browser data, and environment variables.
The forward risk is persistence across dependent projects. Once these packages land in build or developer environments, the compromise can reach wallet access and cloud tokens across multiple projects, not just one infected machine.