Malicious Code Injection in rino-poke33: A Threat to npm Ecosystem
Summary
MAL-2025-164678: Malicious code in rino-poke33 (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
rino-poke33 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 through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants that can clutter the npm registry.
Vulnerability Detail
The vulnerability in rino-poke33 originates from its design to execute autopublish scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages. The continuous republishing of these variants can lead to a polluted ecosystem, making it difficult for developers to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rino-poke33If 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 rino-poke33 package and monitor your project's dependencies for any malicious activity. Implementing a tool like Vulert can help you track vulnerabilities in your open-source packages. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.
Conclusion
The rino-poke33 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and republish variants. It is essential for developers to be vigilant, regularly monitor their dependencies, and utilize tools like Vulert to safeguard their projects from such vulnerabilities.
See every vulnerability recorded for rino-poke33 →
FAQ
rino-poke33 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability allows malicious code to modify your package.json file, potentially leading to the installation of compromised packages and a polluted npm registry.
You should uninstall the rino-poke33 package immediately using the command npm uninstall rino-poke33 and check your project for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. The Vulert playground allows you to check your application for vulnerabilities without any signup.
There are no patches available for rino-poke33 as it is a malicious package. The best course of action is to remove it from your project.
