Malicious Code Injection in rival-poke33: A Threat to npm Packages
Summary
MAL-2025-165015: Malicious code in rival-poke33 (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-poke33 is an npm package that has been implicated in a malicious campaign targeting the npm registry. This package is part of a broader initiative that aims to exploit the npm ecosystem by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the registry and compromise the integrity of legitimate packages.
Vulnerability Detail
The vulnerability in rival-poke33 originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the affected package but also contributes to the overall degradation of the npm registry by continuously republishing variants, making it difficult for developers to trust the integrity of packages. The ramifications include potential exposure to further malicious code and a polluted package ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke33If 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 measure, avoid using rival-poke33 and any packages that depend on it. Regularly audit your package-lock.json file to identify and remove any instances of this malicious package. You can also utilize tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.
Conclusion
The rival-poke33 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and monitor for similar vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for rival-poke33 →
FAQ
rival-poke33 is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the package immediately using the command npm uninstall rival-poke33 and check for any dependencies that may be affected.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
Regularly audit your dependencies, use trusted sources for packages, and implement security tools like Vulert to stay informed about vulnerabilities.
