Malicious Code Injection in adjacent_cicada-appteadev Package
Summary
MAL-2025-99177: Malicious code in adjacent_cicada-appteadev (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 adjacent_cicada-appteadev package is part of the npm ecosystem, which is widely used for JavaScript development. This package was identified as part of a malicious campaign that aimed to exploit npm's publishing capabilities. It is designed to generate and publish derivative packages with random names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and users relying on its functionality.
Vulnerability Detail
The vulnerability originates from the package being part of a token reward campaign that floods the npm registry with malicious packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and create random package names. This results in the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The ramifications include loss of trust in the npm ecosystem and potential security risks for applications using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall adjacent_cicada-appteadevIf 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 workaround, you can monitor your package dependencies using tools like Vulert, which allows you to check for vulnerabilities in your application without requiring code access or installation. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.
Conclusion
The adjacent_cicada-appteadev package poses a significant security risk due to its malicious nature. It is crucial for developers to be vigilant about their dependencies and take immediate action to remove any affected packages. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for adjacent_cicada-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your application if it relies on this package.
You should uninstall the adjacent_cicada-appteadev package immediately and monitor your dependencies for any vulnerabilities.
Yes, you can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without any signup.
