Malicious Code Injection in rival-poke74: A Threat to npm Users
Summary
MAL-2025-165060: Malicious code in rival-poke74 (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 package 'rival-poke74' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, specifically for the tea.xyz protocol. The malicious nature of this package lies in its ability to modify essential files and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'rival-poke74' originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to significant ramifications, including the potential for developers to unknowingly install malicious packages, which can compromise their applications and systems. The technical aspects involve the manipulation of package metadata and the continuous republishing of these malicious variants, making it difficult to track and remove them from the registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke74If 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-poke74' package and any other packages that may have been published as part of the same malicious campaign. It is advisable to review your package-lock.json file for any suspicious entries and remove them accordingly.
Conclusion
The 'rival-poke74' package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and flood the npm registry. It is essential to take immediate action by uninstalling the package and monitoring your dependencies to ensure the security of your applications.
See every vulnerability recorded for rival-poke74 →
FAQ
The 'rival-poke74' package is an npm package identified as part of a malicious campaign that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected by this vulnerability.
The risks include the potential for installing malicious packages, which can compromise application security and lead to unauthorized access or data breaches.
There is no patch available for 'rival-poke74' as it is recommended to uninstall the package entirely to mitigate the risk.
Regularly update your dependencies, monitor your package-lock.json file for suspicious packages, and utilize tools like Vulert to stay informed about vulnerabilities.
