@fairwords/loopback-connector-esnpm
Malicious code in @fairwords/loopback-connector-es (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
The @fairwords/loopback-connector-es package was compromised as part of the TeamPCP/CanisterWorm campaign. A postinstall hook executes node scripts/check-env.js || true which performs multi-stage credential harvesting, encrypted exfiltration, and self-propagation.
The payload harvests 40+ environment variable patterns (AWS, Azure, GCP, GitHub, OpenAI, Stripe), reads 30+ filesystem credential locations (SSH keys, .npmrc, Kubernetes configs, Docker auth, Terraform files), steals crypto wallet data (Solana, Ethereum, Bitcoin, MetaMask, Phantom, Exodus, Atomic Wallet), and extracts Chrome passwords on Linux via hardcoded PBKDF2 key derivation.
Exfiltration uses a RSA-4096 + AES-256-CBC hybrid encryption scheme, sending data to an HTTPS C2 endpoint (telemetry.api-monitor.com) and an Internet Computer (ICP) canister as a decentralized dead-drop.
The worm steals npm tokens to enumerate and infect all publishable packages owned by the token holder, auto-publishing with bumped version numbers. It also performs cross-ecosystem propagation to PyPI via .pth file injection.
Version 1.4.4 was auto-published ~8 minutes after the initial compromise of version 1.4.3, containing a variant propagation payload.
The package @fairwords/loopback-connector-es was found to contain malicious code.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @fairwords/loopback-connector-es (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @fairwords/loopback-connector-es across your stack and pipelines.
If you installed it — respond
@fairwords/loopback-connector-es is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @fairwords/loopback-connector-es was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @fairwords/loopback-connector-es before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
References
Credits
- Amazon Inspector · finder
- SafeDep · finder
Detect & block this
O3 blocks @fairwords/loopback-connector-es-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.