Malicious Code Injection in rival-poke46: A Threat to npm Ecosystem
Summary
MAL-2025-165029: Malicious code in rival-poke46 (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-poke46 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to exploit the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary function appears to be to inflate developer reputation scores in exchange for token rewards associated with the tea.xyz protocol. The package's malicious behavior compromises the integrity of the npm registry and can lead to widespread issues for developers relying on legitimate packages.
Vulnerability Detail
The vulnerability in rival-poke46 stems from its inclusion in a campaign that utilizes autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and create random package names, which are then continuously republished to the npm registry. This behavior not only pollutes the registry but also poses risks to developers who may inadvertently install these malicious packages, leading to potential 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-poke46If 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-poke46 and any other packages that are part of the malicious campaign. Regularly audit your package-lock.json file to identify and remove any suspicious packages. You can also use tools like Vulert to monitor your dependencies for vulnerabilities. For example, you can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The discovery of malicious code in the rival-poke46 package highlights the ongoing risks within the npm ecosystem. Developers must remain vigilant by regularly auditing their dependencies and utilizing tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential threats.
See every vulnerability recorded for rival-poke46 →
FAQ
rival-poke46 is an npm package identified as part of a malicious campaign that modifies and republishes packages to inflate developer reputation scores.
The vulnerability can lead to the installation of malicious packages, compromising the security and integrity of your project.
You should uninstall rival-poke46 immediately using the command 'npm uninstall rival-poke46' and audit your dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit https://vulert.com for more information.
Regularly audit your dependencies, use trusted packages, and stay updated with the latest security advisories to minimize the risk of vulnerabilities.
