Malicious Code Injection in rival-poke29: A Threat to npm Users
Summary
MAL-2025-165010: Malicious code in rival-poke29 (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-poke29 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to exploit the npm ecosystem by generating and publishing numerous derivative packages with altered metadata. Its primary function is to inflate developer reputation scores for token rewards associated with the tea.xyz protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in rival-poke29 originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, leading to potential security breaches and loss of data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke29If 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-poke29 and any packages that depend on it. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The discovery of malicious code in the rival-poke29 package highlights the importance of vigilance in the npm ecosystem. Developers should take proactive measures to secure their projects by regularly auditing dependencies and utilizing tools like Vulert to monitor for vulnerabilities. By staying informed and acting swiftly, developers can protect their applications from potential threats.
See every vulnerability recorded for rival-poke29 →
FAQ
rival-poke29 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the installation of malicious packages that compromise your project's security and integrity, potentially exposing sensitive data.
You can use Vulert, a tool that monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities in real-time. You can also check your application using the Vulert playground at Vulert Scanner without needing to sign up.
Immediately uninstall the rival-poke29 package using npm uninstall rival-poke29 and audit your project for any other potentially malicious dependencies.
Currently, there is no specific patch for rival-poke29. The best course of action is to remove the package and monitor for updates from the npm community.
