This threat is a supply chain attack campaign distributing malicious packages through npm and PyPI, targeting developers, especially in bioinformatics and MCP development. It uses three delivery mechanisms: executable .pth startup hooks, trojanized native .abi3.so extensions that execute upon import, and a split loader-payload architecture that searches Python's sys.path. Twenty-three PyPI packages masquerade as legitimate tools and popular libraries. The malware includes obfuscated JavaScript stealers running in the Bun runtime environment, aiming to steal high-value credentials such as GitHub tokens, npm registry credentials, cloud access keys, SSH keys, and CI/CD secrets. Anti-analysis techniques include fake LLM prompt-injection headers to evade AI-based security detection. The campaign targets developer workstations and automated build systems, posing a medium severity risk. No CVE or known exploits in the wild are reported, and no patch or remediation guidance is provided.

The attack compromises developer environments by stealing sensitive credentials including GitHub tokens, npm registry access, cloud credentials, SSH keys, and CI/CD secrets. This can lead to unauthorized access to source code repositories, package registries, cloud infrastructure, and continuous integration/deployment pipelines. The use of obfuscated JavaScript stealers and anti-analysis techniques increases the difficulty of detection and mitigation. The campaign affects a broad range of packages, including those used in bioinformatics and AI development, potentially impacting supply chain integrity and developer trust.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. In the absence of official fixes, developers should carefully audit dependencies, avoid installing packages from untrusted sources, and monitor for suspicious activity related to credential use. Employing multi-factor authentication and rotating credentials regularly can reduce risk. Use security tools capable of detecting obfuscated code and supply chain threats. Given the anti-analysis techniques used, relying solely on AI-assisted scanners may be insufficient. Organizations should consider additional manual review and behavioral monitoring of developer environments and build pipelines.