Malicious Code Injection in rinto-poke31: A Threat to npm Ecosystem
Summary
MAL-2025-164802: Malicious code in rinto-poke31 (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-poke31 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores by flooding the npm registry with derivative packages. The package is designed to automate the generation and publication of these derivative packages, potentially compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in rinto-poke31 stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the affected package but also poses a risk to developers relying on the integrity of the npm ecosystem, leading to potential security breaches and reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rinto-poke31If 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 rinto-poke31 package and monitor your project for any dependencies that may have been affected by this malicious code. Regularly check your package-lock.json file for any suspicious entries.
Conclusion
The rinto-poke31 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and flood the registry with derivative packages. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for rinto-poke31 →
FAQ
rinto-poke31 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability allows the package to modify your project's package.json file, potentially leading to security breaches and the introduction of malicious code into your project.
If you have installed rinto-poke31, you should uninstall it immediately using the command npm uninstall rinto-poke31 and review your project for any other affected dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
There are no patches available for rinto-poke31 as it is a malicious package. The best course of action is to remove it from your project.
