Malicious Code Injection in Comprehensive Slug Violet-67: A Threat to npm Packages
Summary
MAL-2025-100795: Malicious code in comprehensive_slug_violet-67 (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
Comprehensive Slug Violet-67 is an npm package that has been implicated in a malicious campaign targeting the npm ecosystem. This package is part of a larger scheme associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the comprehensive_slug_violet-67 package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly use these compromised packages. The ramifications include loss of trust in the npm ecosystem, potential data breaches, and the risk of further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall comprehensive_slug_violet-67If 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 avoid using the comprehensive_slug_violet-67 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The comprehensive_slug_violet-67 package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package from their projects and monitor their applications for vulnerabilities using tools like Vulert.
See every vulnerability recorded for comprehensive_slug_violet-67 →
FAQ
Comprehensive_slug_violet-67 is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.
The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to pollution of the npm registry and potential security risks.
You should uninstall the package immediately using 'npm uninstall comprehensive_slug_violet-67' and check for any alternative packages.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
