This threat involves a multi-stage malware campaign targeting the npm supply chain ecosystem. Initially marked by the Shai-Hulud worm in September 2025, the attack evolved into a coordinated campaign by TeamPCP in April 2026 using a malicious @bitwarden/cli package. The malware propagates through multiple developer and CI/CD distribution channels, harvesting credentials and exfiltrating data via encrypted HTTPS and GitHub repositories. It self-replicates by injecting backdoors into npm packages using stolen tokens. The malware leverages GitHub's search API as a resilient fallback for command-and-control and employs anti-detection measures including locale-based killswitches. This campaign demonstrates advanced supply chain compromise techniques with wormable propagation and dormant payload activation under specific conditions. No patch or official remediation is documented, and no confirmed exploits in the wild are reported.

The malware compromises developer environments and supply chain infrastructure by harvesting credentials from cloud providers and workstations, enabling persistent access and data exfiltration. It can propagate autonomously by backdooring npm packages, potentially affecting multiple downstream projects and users. The use of encrypted communication and fallback C2 mechanisms increases its resilience and stealth. The presence of anti-detection features complicates detection and response efforts. Although no known exploits in the wild are confirmed, the potential impact on software supply chains and developer ecosystems is significant.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Due to the lack of official patches or fixes, organizations should monitor trusted vendor advisories and threat intelligence updates for mitigation recommendations. Focus on verifying the integrity of npm packages, restricting token permissions, and scrutinizing CI/CD pipeline security. Avoid using suspicious or unverified npm packages, especially those related to @bitwarden/cli. Employ threat intelligence indicators such as known malicious domains and hashes to detect potential compromise. No vendor advisory states that no action is required or that the threat is already mitigated.