Which versions of passwordcracker are malicious?

Every published version of passwordcracker on npm is considered malicious. Remove the package entirely.

How do I remediate passwordcracker if I installed it?

Remove passwordcracker from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed passwordcracker — how do I know if it already compromised me?

If passwordcracker 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.

How do I find passwordcracker across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for passwordcracker (all published versions).

Malicious package

passwordcrackernpm

Advisory published Oct 10, 2026Updated Oct 14, 2026

passwordcracker is a confirmed malicious npm package (MAL-2026-17864) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in passwordcracker (npm)

MAL-2026-17864

Immediate action

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

npm uninstall passwordcracker

What this malware does

passwordcracker poses as a dependency-free Discord MFA library but pulls node-net-pool from the attacker's GitHub repo lunexindonesia/node-net-pool, and on load lib/cache.js runs try{module['require']('node-net-pool')}catch(_){} to execute it. On Windows, that index.js downloads a script from a limbomail.com attachment URL, saves it as a hidden winsvc.js under %APPDATA%, %LOCALAPPDATA% or %TEMP%, runs it via a hidden WinSvcHost.vbs, persists through HKCU Run/RunOnce, UserInitMprLogonScript and a Startup shortcut, and re-checks for updates every two hours. Amazon Inspector reported the same loader stub in discord-mfa-solver (MAL-2026-16100). The npm account kingsize published passwordcracker and passwordcrackv2 with identical code on 2026-10-09 and 2026-10-10.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for passwordcracker (all published versions).
If you installed it — respond
Remove passwordcracker from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If passwordcracker 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. passwordcracker on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

InvisiRisk, Inc. · finder

Detect & block this

O3 blocks passwordcracker-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database