Malicious Code Injection in rinto-poke29: A Threat to npm Ecosystem
Summary
MAL-2025-164799: Malicious code in rinto-poke29 (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
rinto-poke29 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to participate in the tea.xyz token reward scheme, 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 modify critical files and continuously republish variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in rinto-poke29 originates from its involvement in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages. The payload modifies the package.json file to remove private flags, alters version numbers, and creates random package names, which can lead to further exploitation and confusion within the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rinto-poke29If 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 the rinto-poke29 package and monitor your project for any unintended installations. You can also use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The rinto-poke29 package poses a significant threat to the npm ecosystem due to its malicious behavior of generating and publishing derivative packages. It is crucial for developers to be vigilant and remove such packages from their projects to maintain security and integrity. Utilizing tools like Vulert can aid in monitoring for vulnerabilities effectively.
See every vulnerability recorded for rinto-poke29 →
FAQ
rinto-poke29 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security, potentially allowing for further exploitation.
You should immediately uninstall the rinto-poke29 package using 'npm uninstall rinto-poke29' and check your project for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues.
There is no patch available for rinto-poke29 as it is a malicious package. The best course of action is to remove it from your project.
