# MAL-2026-2507: Malicious code in @fairwords/loopback-connector-es (npm)


- **Type:** Malicious package
- **Package:** `@fairwords/loopback-connector-es` (npm)
- **Published:** 8 Apr 2026

## What is MAL-2026-2507?

MAL-2026-2507 is a malicious package in @fairwords/loopback-connector-es, published on 8 Apr 2026. 

### Official description

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.

## What should I do about MAL-2026-2507?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-2507 is a malicious package: @fairwords/loopback-connector-es (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-2507/ (Markdown: https://insights.sbomify.com/MAL-2026-2507/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-2507

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-2507/
Summaries are generated and may contain mistakes; the official description above is the record.