Malicious Code Injection in dennis-validator-catalyst: A Threat to npm Users
Summary
MAL-2025-101344: Malicious code in dennis-validator-catalyst (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
dennis-validator-catalyst is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages. However, it has been compromised to include malicious scripts that can manipulate package metadata and flood the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the dennis-validator-catalyst package. This payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names. The intent is to inflate developer reputation scores for token rewards while polluting the npm registry with numerous derivative packages. This can lead to security risks, including the potential for dependency confusion and misuse of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dennis-validator-catalystIf 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 dennis-validator-catalyst package from your project by running: npm uninstall dennis-validator-catalyst. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The dennis-validator-catalyst package has been identified as containing malicious code that can compromise npm projects. It is essential for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for dennis-validator-catalyst →
FAQ
The malicious code can lead to the unauthorized modification of your package.json file, potentially exposing your project to further vulnerabilities and dependency issues.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json, it can provide real-time alerts for any vulnerabilities.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Additionally, avoid using packages from untrusted sources.
If you suspect that your project has been compromised, immediately remove the affected package and review your project for any unauthorized changes. Consider restoring from a backup if necessary.
You can find detailed information about this vulnerability in the official npm advisory or by visiting the GitHub repository of the affected package.
