NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@fairwords/loopback-connector-esnpm

Advisory published Updated

@fairwords/loopback-connector-es is a confirmed malicious npm package (MAL-2026-2507) that steals credentials and exfiltrates sensitive data (malicious versions 1.4.3, 1.4.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @fairwords/loopback-connector-es (npm)

MAL-2026-2507
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @fairwords/loopback-connector-es

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

2 flagged
1.4.31.4.4

Indicators of compromise (SHA-256)

cd2a0ea00b47edd8b7d883321de362596fd973c55e9278eb8a6590b752ebbdf1

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @fairwords/loopback-connector-es (2 malicious versions).

  2. 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.

  3. Did it already run?

    If @fairwords/loopback-connector-es was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @fairwords/loopback-connector-es on npm has been identified as a malicious package (versions 1.4.3, 1.4.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@fairwords/loopback-connector-es (npm) malicious package — MAL-2026-2507 | O3 Security