Malicious Code Injection in prime_cuckoo-silentdev Package
Summary
MAL-2025-107264: Malicious code in prime_cuckoo-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 prime_cuckoo-silentdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts designed to automatically publish derivative packages with altered metadata, including the removal of private flags and the generation of random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can lead to unauthorized access and manipulation of projects that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall prime_cuckoo-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 prime_cuckoo-silentdev package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before including them in your project.
Conclusion
The prime_cuckoo-silentdev package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your projects.
See every vulnerability recorded for prime_cuckoo-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic publishing of derivative packages.
If your application depends on the prime_cuckoo-silentdev package, it may be at risk of unauthorized modifications and exposure to malicious code.
You should immediately uninstall the prime_cuckoo-silentdev package using the command npm uninstall prime_cuckoo-silentdev and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against known vulnerabilities using the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
