Critical Malicious Code Vulnerability in yargs-js Package

yargs-js Updated 12 Jan 2026

Summary

12/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-207: Malicious code in yargs-js (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

yargs-js is a popular Node.js library used for building command-line interfaces. It allows developers to parse command-line arguments and provides a rich set of features for handling input. However, the package has been compromised, leading to a serious security vulnerability that can affect any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the yargs-js package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has inserted harmful code into the package, which poses a significant risk to users and their data.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall yargs-js

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, you can temporarily avoid using the yargs-js package by replacing it with alternative libraries for command-line argument parsing, such as 'commander' or 'minimist'. However, this does not eliminate the need to remove the compromised package.

Conclusion

The yargs-js package has been compromised with malicious code, posing a severe risk to users. Immediate action is required to remove the package and secure any sensitive information. Stay vigilant and consider using tools like Vulert to monitor for vulnerabilities in your applications.

See every vulnerability recorded for yargs-js →

Share this vulnerability

FAQ

Immediately remove the yargs-js package from your system and rotate any sensitive information stored on the affected machine.

You can use Vulert to monitor and alert for open-source vulnerabilities. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

You should not use yargs-js until a secure version is released. Consider using alternative libraries for your command-line interface needs.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall yargs-js

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback