Malicious Code Injection in symbolic_cicada-silentdev Package
Summary
MAL-2025-109426: Malicious code in symbolic_cicada-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 symbolic_cicada-silentdev package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the symbolic_cicada-silentdev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages. The malicious behavior can compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall symbolic_cicada-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 remove the symbolic_cicada-silentdev package from your project by executing: npm uninstall symbolic_cicada-silentdev. This will prevent the malicious code from executing until a fixed version is available.
Conclusion
The symbolic_cicada-silentdev package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for symbolic_cicada-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
The malicious code can alter your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry.
You should uninstall the symbolic_cicada-silentdev package immediately and check for any updates or patches that may be available.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
