Malicious Code Injection in rival-poke58: A Threat to npm Ecosystem
Summary
MAL-2025-165042: Malicious code in rival-poke58 (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-poke58 is an npm package that has been identified as part of a broader malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package poses significant risks to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in rival-poke58 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also compromises the security and reliability of applications that depend on these packages. The continuous republishing of variants can lead to a loss of trust in the npm ecosystem and potential exploitation of affected applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke58If 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-poke58 and any other packages associated with the tea.xyz campaign. Instead, consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The discovery of malicious code in the rival-poke58 package highlights the ongoing risks associated with open-source software. Developers must remain vigilant and proactive in managing their dependencies to ensure the security and integrity of their applications. By removing vulnerable packages and utilizing tools like Vulert, developers can better protect their projects from potential threats.
See every vulnerability recorded for rival-poke58 →
FAQ
rival-poke58 is an npm package identified as part of a malicious campaign that manipulates developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the injection of malicious code into your application, compromising its security and potentially leading to data breaches or other exploits.
You should uninstall the rival-poke58 package immediately using the command 'npm uninstall rival-poke58' and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, you should look for well-reviewed and actively maintained packages that provide similar functionality without the risks associated with rival-poke58.
