Malicious Code Injection in rino-poke62: A Threat to npm Ecosystem

rino-poke62 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164710: Malicious code in rino-poke62 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

rino-poke62 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores through the generation and publication of derivative packages. Its primary functionality revolves around token reward systems, which incentivize developers to publish more packages, often leading to the proliferation of harmful software.

Vulnerability Detail

The vulnerability in rino-poke62 stems from its inclusion in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package 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 variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores through deceptive practices.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rino-poke62

If 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, avoid using the rino-poke62 package and monitor your project for any unexpected behavior. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The rino-poke62 package poses a significant risk due to its malicious code designed to manipulate npm registry practices. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure development environment.

See every vulnerability recorded for rino-poke62 →

Share this vulnerability

FAQ

rino-poke62 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to the installation of malicious packages that compromise the integrity of your project and the npm registry.

You should uninstall the rino-poke62 package immediately using 'npm uninstall rino-poke62' and check for any other affected packages.

You can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without needing to install any software.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rino-poke62

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback