Malicious Code Vulnerability in rino-poke17: npm Package Exploit

rino-poke17 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164660: Malicious code in rino-poke17 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

rino-poke17 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been compromised to include malicious scripts that manipulate package metadata and flood the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability in rino-poke17 stems from its inclusion in a malicious campaign that aims to inflate developer reputation scores through the automatic generation of numerous derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and creating random package names, which leads to pollution of the npm registry and potential security risks for users who inadvertently install these variants.

How To Fix

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

npm uninstall rino-poke17

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 workaround, avoid using the rino-poke17 package and consider alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies to identify and remove any potentially malicious packages.

Conclusion

The rino-poke17 package has been identified as containing malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor your dependencies for any similar vulnerabilities. Utilizing tools like Vulert can help keep your software secure.

See every vulnerability recorded for rino-poke17 →

Share this vulnerability

FAQ

rino-poke17 is an npm package involved in a token reward campaign that has been compromised to include malicious code.

The malicious code modifies your package.json file, removes private flags, and floods the npm registry with unwanted package variants, which can lead to security vulnerabilities.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

You should uninstall the rino-poke17 package immediately using the command: npm uninstall rino-poke17 and check for any dependencies that may rely on it.

Yes, consider using other npm packages that provide similar functionality without the associated risks. Always review package reputations before installation.

How To Fix

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

npm uninstall rino-poke17

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