Malicious Code Vulnerability in publish-superagent-rollup-plugin-commitlint
Summary
MAL-2025-188958: Malicious code in publish-superagent-rollup-plugin-commitlint (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'publish-superagent-rollup-plugin-commitlint' is part of the npm ecosystem, designed to facilitate the integration of commit linting in projects using Superagent and Rollup. However, it has been compromised as part of a broader malicious campaign targeting npm packages, leading to significant security concerns.
Vulnerability Detail
This vulnerability originates from a malicious payload embedded within the package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The intent is to inflate developer reputation scores through the automatic publication of derivative packages, thereby polluting the npm registry. This can lead to unauthorized access, potential data breaches, and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall publish-superagent-rollup-plugin-commitlintIf 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 affected package from your project by executing 'npm uninstall publish-superagent-rollup-plugin-commitlint'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'publish-superagent-rollup-plugin-commitlint' package has been compromised, leading to a significant vulnerability that can affect your development environment. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.
See every vulnerability recorded for publish-superagent-rollup-plugin-commitlint →
FAQ
The malicious code modifies package.json to remove private flags and generates random package names to inflate developer reputation scores.
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.
The risks include unauthorized access to your project, potential data breaches, and the pollution of the npm registry with malicious packages.
Regularly audit your dependencies, use tools like Vulert for monitoring, and ensure that you only install packages from trusted sources.
If an immediate update is not possible, consider removing the package temporarily and monitor for any updates or patches from the maintainers.
