Malicious Code Injection in rino-poke39: A Threat to npm Ecosystem
Summary
MAL-2025-164684: Malicious code in rino-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
rino-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 rino-poke39 lies in its ability to modify package metadata and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in rino-poke39 originates from its design to include autopublish scripts that automatically generate and publish 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 use these malicious packages. The payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to confusion and potential security risks for users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rino-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, avoid using the rino-poke39 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The rino-poke39 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for rino-poke39 →
FAQ
rino-poke39 is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation 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 rino-poke39 package immediately using the command npm uninstall rino-poke39 and review your project's dependencies for any other vulnerabilities.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
