Malicious Code Detected in commodity-node Package - MAL-2025-17425

commodity-node Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17425: Malicious code in commodity-node (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The commodity-node package is a Node.js library that provides a simple interface for generating and manipulating commodity data. It is widely used in applications requiring data handling and processing. However, this package has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the commodity-node package stems from the inclusion of malicious code that can compromise the security and integrity of applications utilizing this package. This code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The malicious code was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall commodity-node

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 measure, you can remove the commodity-node package from your project if it is not essential. Use the following command to uninstall it: npm uninstall commodity-node. Alternatively, consider using a different package that offers similar functionality without the security risks.

Conclusion

The discovery of malicious code in the commodity-node package poses a serious threat to users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for commodity-node →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential exploitation of systems using the commodity-node package.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Simply upload your package-lock.json file to check for vulnerabilities.

As of now, there is no specific patched version mentioned. It is advisable to remove the package or switch to an alternative until a secure version is released.

Immediately remove the package and assess your application for any potential security breaches. Consider using an alternative package.

Yes, you can use the Vulert playground to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall commodity-node

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.