Which versions of @wethenorth12/crypto-config are malicious?

The following npm versions of @wethenorth12/crypto-config are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate @wethenorth12/crypto-config if I installed it?

@wethenorth12/crypto-config 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 @wethenorth12/crypto-config — how do I know if it already compromised me?

If @wethenorth12/crypto-config 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.

Is @wethenorth12/crypto-config part of a known attack campaign?

Yes — @wethenorth12/crypto-config is associated with the IN-MAL-2026-013453 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 @wethenorth12/crypto-config across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @wethenorth12/crypto-config (version 2.0.1).

Part of a larger attack: @wethenorth12 published 23 malicious packages. See the full campaign →

Malicious package

@wethenorth12/crypto-confignpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

@wethenorth12/crypto-config is a confirmed malicious npm package (MAL-2026-12089) that steals credentials and exfiltrates sensitive data (malicious version 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wethenorth12/crypto-config (npm)

MAL-2026-12089

Immediate action

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

npm uninstall @wethenorth12/crypto-config

What this malware does

On require, index.js collects process.env, hostname, username, homedir, platform, and cwd, base64-encodes the blob, and POSTs it to api.telegram.org/bot<token>/sendMessage with a hardcoded bot token and chat_id 8969499041. A tmp marker file gates repeat sends. The package presents itself as a drop-in for the popular config package (typosquat), attempts to require('config') and re-exports it to preserve apparent functionality, and uses randomized variable names to obscure the exfiltration path.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

d56f2c55cacbd8d06b8d3b0f20b808262c42cd002441399d8e39a2f03c600f3c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @wethenorth12/crypto-config (version 2.0.1).
If you installed it — respond
@wethenorth12/crypto-config 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 @wethenorth12/crypto-config 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. @wethenorth12/crypto-config on npm has been identified as a malicious package (version 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-013453

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wethenorth12/crypto-config-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