Malicious Code Injection in constant_lobster-silentdev Package
Summary
MAL-2025-100886: Malicious code in constant_lobster-silentdev (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 constant_lobster-silentdev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and security.
Vulnerability Detail
The vulnerability originates from the package's involvement in a scheme that floods the npm registry with derivative packages. It includes autopublish scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry and poses significant risks, including the potential for malicious actors to exploit these packages for nefarious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall constant_lobster-silentdevIf 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 constant_lobster-silentdev package altogether. If it is already in use, consider replacing it with a trusted alternative that does not exhibit malicious behavior.
Conclusion
The constant_lobster-silentdev package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to ensure security.
See every vulnerability recorded for constant_lobster-silentdev →
FAQ
It is an npm package involved in the tea.xyz token reward campaign, designed to automatically generate and publish derivative packages.
The vulnerability can lead to the pollution of the npm registry and may expose your project to malicious code and security risks.
You should remove the constant_lobster-silentdev package from your project and check for any updates or alternatives.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
