Malicious Code Injection in rinto-poke39: A Threat to npm Ecosystem
Summary
MAL-2025-164810: Malicious code in rinto-poke39 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
rinto-poke39 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm ecosystem by introducing harmful scripts and altering package metadata.
Vulnerability Detail
The vulnerability in rinto-poke39 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file to remove private flags and change version numbers. The potential ramifications include the proliferation of malicious packages that can mislead developers and compromise their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rinto-poke39If 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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which analyzes your package-lock.json file to identify vulnerabilities in real-time. 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 rinto-poke39 package poses a significant threat to the npm ecosystem due to its malicious code and behavior. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to protect their projects. By uninstalling the affected package and utilizing tools like Vulert, developers can enhance their security posture and mitigate risks associated with open-source dependencies.
See every vulnerability recorded for rinto-poke39 →
FAQ
rinto-poke39 is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic publication of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the rinto-poke39 package immediately and check for any dependencies that may be affected.
Yes, tools like Vulert can help monitor your project's dependencies for vulnerabilities by analyzing the package-lock.json file.
Regularly update your dependencies, use trusted packages, and utilize vulnerability monitoring tools like Vulert to stay informed about potential threats.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
