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

rino-poke7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164718: Malicious code in rino-poke7 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

rino-poke7 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-poke7 lies in its ability to modify package metadata and republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in rino-poke7 stems from its integration into a broader malicious scheme that utilizes autopublish scripts to create and disseminate numerous derivative packages. These scripts alter the package.json file by removing private flags, changing version numbers, and generating random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall rino-poke7

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, you can avoid using the rino-poke7 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to identify and remove any potentially malicious packages.

Conclusion

The rino-poke7 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive steps to remove affected packages and stay updated with the latest versions will help safeguard applications from potential security risks.

See every vulnerability recorded for rino-poke7 →

Share this vulnerability

FAQ

rino-poke7 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of malicious code that modifies your package metadata and potentially compromises your application's security.

You should immediately uninstall the rino-poke7 package using the command npm uninstall rino-poke7 and audit your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can also check for vulnerabilities using the Vulert playground without any signup.

Yes, tools like Vulert provide real-time monitoring for vulnerabilities in your open-source dependencies, helping you maintain a secure application.

How To Fix

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

npm uninstall rino-poke7

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