Malicious Code Injection in rival-poke11: A Threat to npm Users
Summary
MAL-2025-164989: Malicious code in rival-poke11 (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
rival-poke11 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify its own metadata and continuously republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in rival-poke11 stems from its malicious payload that alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke11If 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 rival-poke11 and any packages that may have been derived from it. Regularly audit your package-lock.json file for any suspicious entries or dependencies that may have been introduced without your knowledge.
Conclusion
The rival-poke11 package poses a significant threat to npm users due to its malicious behavior of modifying package metadata and republishing itself. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying vigilant and regularly auditing your dependencies can help maintain the security of your applications.
See every vulnerability recorded for rival-poke11 →
FAQ
rival-poke11 is an npm package identified as part of a malicious campaign that modifies package metadata and repackages itself under various names.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and functionality.
Immediately uninstall the rival-poke11 package and review your project's dependencies for any other potentially compromised packages.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
