Malicious Code Injection in rival-poke27: A Threat to npm Users
Summary
MAL-2025-165008: Malicious code in rival-poke27 (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-poke27 is an npm package that has been identified as part of a malicious campaign targeting developers in the npm ecosystem. 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 manipulate the npm registry by creating numerous variants of itself, thereby polluting the registry and potentially compromising user projects.
Vulnerability Detail
The vulnerability in rival-poke27 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, which can lead to the unintended exposure of sensitive information and the proliferation of untrustworthy packages in the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to gain undue advantages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke27If 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, you can avoid using rival-poke27 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package-lock.json file to identify and remove any suspicious packages.
Conclusion
The rival-poke27 package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial to take immediate action by uninstalling the package and monitoring your project for any other vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for rival-poke27 →
FAQ
rival-poke27 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
This vulnerability can lead to the exposure of sensitive information and the introduction of untrustworthy packages into your project, potentially compromising its integrity.
You should immediately uninstall the rival-poke27 package using the command npm uninstall rival-poke27 and review your project for any other suspicious 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 against known vulnerabilities using the Vulert playground at Vulert Scanner.
Regularly audit your dependencies, keep them updated, and use trusted sources for package installations to minimize the risk of vulnerabilities.
