Malicious Code Injection in rival-poke60: A Threat to npm Users
Summary
MAL-2025-165045: Malicious code in rival-poke60 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The rival-poke60 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability in rival-poke60 stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards in the tea.xyz protocol. The malicious payload continuously republishes variants, polluting the npm registry and potentially compromising other packages that depend on it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke60If 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-poke60 and any packages that depend on it. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The rival-poke60 package poses a significant security risk due to its malicious code that alters package metadata and repackages itself. It is essential for developers to remove this package and regularly audit their dependencies to ensure the security of their applications. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for rival-poke60 →
FAQ
The vulnerability involves malicious code that modifies package metadata and repackages it under random names, leading to potential security risks.
You can use the Vulert platform to monitor your application for vulnerabilities. Simply upload your package-lock.json file at Vulert Scanner to check for any affected packages.
You should immediately uninstall the rival-poke60 package and review your project's dependencies for any other potentially malicious packages.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
Using compromised packages can lead to security breaches, data leaks, and the potential for malicious actors to gain control over your application.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
