Critical Malicious Code Vulnerability in node-argon Package

node-argon Updated 24 Feb 2026

Summary

24/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1011: Malicious code in node-argon (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

node-argon is a popular npm package used for hashing passwords using the Argon2 algorithm. It is designed to provide secure password storage and is widely utilized in various applications for user authentication. However, a recent vulnerability has been identified that compromises the integrity of this package, posing significant risks to systems that rely on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the node-argon package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The malicious code is linked to a specific commit in the package's history, and its presence indicates a severe security breach that could lead to data theft or system manipulation.

How To Fix

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

npm uninstall node-argon

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

There are no direct workarounds to mitigate the effects of this vulnerability. The only effective measure is to uninstall the compromised package and rotate any sensitive information that may have been exposed.

Conclusion

The discovery of malicious code within the node-argon package poses a significant threat to systems utilizing this package for password hashing. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can aid in identifying vulnerabilities in your software ecosystem.

See every vulnerability recorded for node-argon →

Share this vulnerability

FAQ

You should uninstall the node-argon package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Currently, there is no patched version available for node-argon. It is recommended to remove the package and consider alternative solutions.

Failing to address this vulnerability could lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.

Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software, helping you maintain security without needing to access the code directly.

How To Fix

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

npm uninstall node-argon

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