Critical Malicious Code Vulnerability in argonnode Package

argonnode Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1656: Malicious code in argonnode (npm). Affects argonnode versions 2.4.5. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The argonnode package is a Node.js library designed for cryptographic hashing, specifically implementing the Argon2 algorithm. It is widely used for secure password hashing and data protection in various applications. However, the package has been identified to contain malicious code that can compromise the security of applications relying on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the argonnode package, specifically in version 2.4.5. This code can potentially allow unauthorized access to sensitive data or enable remote code execution, posing significant risks to applications using this package. The malicious code was reported by ReversingLabs and is documented in the Open Source Vulnerability database.

How To Fix

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

npm uninstall argonnode

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 temporary workaround, you can remove the argonnode package from your project until a secure version is confirmed. Use the following command to uninstall the package: npm uninstall argonnode.

Conclusion

The argonnode package has been found to contain malicious code that poses significant security risks. It is crucial for developers using this package to update to the latest version or remove it from their projects to protect their applications from potential threats.

See every vulnerability recorded for argonnode →

Share this vulnerability

FAQ

The argonnode package is used for implementing the Argon2 password hashing algorithm in Node.js applications.

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.

The risks include unauthorized access to sensitive data and potential remote code execution, which can compromise the integrity and security of your application.

Yes, updating to the latest version of the argonnode package will address the vulnerability. Use 'npm install argonnode@latest' to update.

If immediate updates are not possible, consider uninstalling the argonnode package as a temporary measure to mitigate risks.

How To Fix

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

npm uninstall argonnode

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