Which versions of mnemonic-utils are malicious?

The following npm versions of mnemonic-utils are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate mnemonic-utils if I installed it?

mnemonic-utils 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 mnemonic-utils — how do I know if it already compromised me?

If mnemonic-utils 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 mnemonic-utils part of a known attack campaign?

Yes — mnemonic-utils is associated with the IN-MAL-2026-013403, IN-MAL-2026-013402, IN-MAL-2026-013418 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 mnemonic-utils 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 mnemonic-utils (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mnemonic-utils across your stack and pipelines.

Malicious package

mnemonic-utilsnpm

mnemonic-utils is a confirmed malicious npm package (MAL-2026-12112) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mnemonic-utils (npm)

MAL-2026-12112

Immediate action

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

npm uninstall mnemonic-utils

What this malware does

index.js executes an IIFE at require-time that reads installer-owned secret files (.env,.npmrc, ~/.aws/credentials, ~/.ssh/id_rsa, id_ed25519, id_ecdsa, Solana id.json, Ethereum keystore) and recursively scans home dotdirectories for files matching /wallet|key|secret|seed|mnemonic|keystore|private/. The harvested contents are combined with os.hostname() and os.userInfo().username into a single JSON body and POSTed over HTTPS to a hardcoded webhook.site URL (path /5c5ad6cb-62df-4ea5-9dfb-2c447920ddc4). The payload is gated by a Date.UTC(2026,7,6) activation check, with in-source comments describing the delay as evasion of npm sandbox detection windows. The package name suggests a mnemonic utility, but the shipped code performs no such function — its only behavior is credential and wallet-secret exfiltration.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

1fa35d474395d73750ae91e7fe420051657623e9a10c517cb06f184f23bc4310

dc209736a2c44e541e224030a4c0bd7145bb77a17fa66504cd96beedc75ce6f4

2cbe05c633f1390b0beffc89dcd60b0ba64f78e9f6b2e32a9f428ac88a295c3e

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 mnemonic-utils (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mnemonic-utils across your stack and pipelines.
If you installed it — respond
mnemonic-utils 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 mnemonic-utils 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 mnemonic-utils 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. mnemonic-utils on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-013403IN-MAL-2026-013402IN-MAL-2026-013418

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mnemonic-utils-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