Which versions of yargsplus are malicious?

The following npm versions of yargsplus are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate yargsplus if I installed it?

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

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

Yes — yargsplus is associated with the IN-MAL-2026-010517 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 yargsplus across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for yargsplus (version 1.0.0).

Malicious package

yargsplusnpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

yargsplus is a confirmed malicious npm package (MAL-2026-10594) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in yargsplus (npm)

MAL-2026-10594

Immediate action

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

npm uninstall yargsplus

What this malware does

The package declares a postinstall hook (node.init.js) that runs automatically on npm install. The script enumerates roughly 60 credential and CI environment variables (including NPM_TOKEN, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, GCP/Azure/Heroku/Vercel/Stripe tokens, DB_PASSWORD), reads home-directory dotfiles such as ~/.npmrc, ~/.env*, and credentials.json, and walks ~/.config for files matching token/cred/secret patterns. It also collects host reconnaissance (hostname, platform, cwd, pid, timestamp) and POSTs the combined JSON to a hardcoded external webhook at webhook.cool. The package ships no legitimate functionality; its main entry is empty. The name resembles the popular yargs CLI parser, consistent with a typosquat lure.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

47ae65e1d6362744681f51216b451ba9889176b3b0c28b1b4c943f1b5033fdd4

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-010517

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks yargsplus-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