Malicious Code Detected in Comma-List Package (npm)

comma-list Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17400: Malicious code in comma-list (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 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 comma-list package is a utility in the npm ecosystem that allows users to handle lists of items in a comma-separated format. It is commonly used in various JavaScript applications for parsing and formatting lists. However, this package has been identified to contain malicious code that poses a security risk to applications utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the comma-list package, which was introduced in version 0 and affects all subsequent versions. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within applications that rely on this package. Users should be aware that the integrity of their applications may be compromised if they continue to use this package.

How To Fix

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

npm uninstall comma-list

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 may consider removing the comma-list package from your project if it is not critical to your application's functionality. You can do this by running the command: 'npm uninstall comma-list'. Alternatively, you can replace it with a different package that offers similar functionality without the security risks.

Conclusion

The discovery of malicious code in the comma-list package highlights the importance of maintaining secure dependencies in software development. Users are urged to update or remove the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for comma-list →

Share this vulnerability

FAQ

Comma-list is an npm package used for handling comma-separated lists in JavaScript applications.

The malicious code was introduced in version 0 of the comma-list package and affects all versions that followed.

Using the compromised package can lead to unauthorized access, data breaches, and potential harm to your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Regularly updating your dependencies and using tools like Vulert to monitor vulnerabilities can help prevent future issues.

How To Fix

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

npm uninstall comma-list

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