Which versions of @fairwords/encryption are malicious?

The following npm versions of @fairwords/encryption are flagged malicious: 0.0.5, 0.0.6. Treat any of these as compromised.

How do I remediate @fairwords/encryption if I installed it?

@fairwords/encryption 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.

I already installed @fairwords/encryption — how do I know if it already compromised me?

If @fairwords/encryption 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.

Is @fairwords/encryption part of a known attack campaign?

Yes — @fairwords/encryption is associated with the GHSA-6rgf-v8fm-jf4g campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @fairwords/encryption across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @fairwords/encryption (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/encryption across your stack and pipelines.

Malicious package

@fairwords/encryptionnpm

Malicious code in @fairwords/encryption (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2506

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @fairwords/encryption

What this malware does

The @fairwords/encryption 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 0.0.6 was auto-published ~8 minutes after the initial compromise of version 0.0.5, containing an incomplete variant propagation payload.

The package @fairwords/encryption was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

0.0.50.0.6

Indicators of compromise (SHA-256)

31a6f300a9557ef3d2dfaeece019b48f526b8c0e40a3881188c67d9f82644831

94883eafca4705628d5f545eb6cb655ceb25228247df96730858304a6cca0f98

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @fairwords/encryption (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/encryption across your stack and pipelines.
If you installed it — respond
@fairwords/encryption 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/encryption 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/encryption 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

No. @fairwords/encryption on npm has been identified as a malicious package (versions 0.0.5, 0.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6rgf-v8fm-jf4g

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @fairwords/encryption-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