Malicious Code Injection in rival-poke53: A Threat to npm Ecosystem
Summary
MAL-2025-165037: Malicious code in rival-poke53 (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-poke53 is an npm package that is part of a broader campaign targeting developers through token rewards. It is designed to facilitate certain functionalities within the npm ecosystem. However, this package has been identified as malicious, containing scripts that manipulate its own package metadata and publish variants to inflate reputation scores fraudulently.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the rival-poke53 package. This code modifies the package.json file to remove private flags and alters version numbers, allowing it to generate and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke53If 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-poke53 package and look for alternative packages that offer similar functionality without the associated risks. Additionally, you can monitor your project for any unexpected changes in the package-lock.json file, which may indicate malicious activity.
Conclusion
The rival-poke53 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and publishes variants. It is essential for developers to uninstall this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain security and integrity in your software development process.
See every vulnerability recorded for rival-poke53 →
FAQ
The malicious code modifies package metadata and publishes numerous variants to inflate developer reputation scores fraudulently.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.
Uninstall the package immediately using 'npm uninstall rival-poke53' and review your project for any dependencies that may rely on it.
Yes, consider researching and using other npm packages that provide similar functionalities without the associated risks.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring your application remains secure.
