Malicious Code Exploit in rival-poke34: npm Package Vulnerability
Summary
MAL-2025-165016: Malicious code in rival-poke34 (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 'rival-poke34' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated publishing scripts, leading to potential security risks.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the 'rival-poke34' package, which contains scripts designed to modify 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 to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these packages, leading to potential exploitation of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke34
If 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 'rival-poke34' package and look for 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 'rival-poke34' package poses a significant security risk due to its malicious code designed to manipulate npm's package registry. It is essential for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications. Regular monitoring and updating of dependencies can help mitigate these risks.
See every vulnerability recorded for rival-poke34 →
FAQ
The 'rival-poke34' package is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through automated publishing.
If your application uses the 'rival-poke34' package, it may be at risk of having its integrity compromised, leading to potential exploitation or data breaches.
You should uninstall the package immediately using 'npm uninstall rival-poke34' and check your application for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.