Malicious Code Injection in Respective Rooster-Appteadev Package
Summary
MAL-2025-107963: Malicious code in respective_rooster-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 respective_rooster-appteadev package is part of the npm ecosystem, primarily used for JavaScript applications. It is often involved in token reward campaigns, which can lead to the proliferation of malicious packages. This package has been identified as part of a larger scheme that aims to inflate developer reputation scores through the automatic generation and publishing of derivative packages.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the respective_rooster-appteadev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to pollute the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages. The ramifications include the risk of code injection, unauthorized access, and the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall respective_rooster-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 temporary workaround, you can avoid using the respective_rooster-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The respective_rooster-appteadev package contains malicious code that poses a significant risk to developers using it. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for respective_rooster-appteadev →
FAQ
It is an npm package that is part of a token reward campaign, which has been identified as containing malicious code.
The malicious code can modify your package.json file, remove private flags, and republish variants, potentially leading to security vulnerabilities.
You should uninstall the package immediately and check for any updates or patches for your other dependencies.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
