Malicious Code Injection in cometseer: A Threat to npm Packages
Summary
MAL-2025-171055: Malicious code in cometseer (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
cometseer is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability in cometseer originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the pollution of the npm registry and can inflate developer reputation scores fraudulently. The implications include potential security risks for applications relying on these packages, as they may inadvertently include malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cometseerIf 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 cometseer package from your project by executing the following command: npm uninstall cometseer. This will prevent any malicious code from being executed until a patch is available.
Conclusion
The cometseer package has been compromised, leading to a significant vulnerability that can affect applications using it. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for cometseer →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Using the compromised package may expose your application to security risks, including the inclusion of malicious code and potential data breaches.
Regularly updating packages, using tools like Vulert for monitoring vulnerabilities, and auditing dependencies can help prevent similar issues.
If immediate updates are not possible, consider removing the package from your project until a secure version is available.
