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

rino-poke4 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164685: Malicious code in rino-poke4 (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-poke4 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards through various automated scripts. However, this package has been identified as malicious, containing scripts that manipulate its own metadata and publish numerous derivative packages to inflate developer reputation scores, ultimately polluting the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious intent to modify its own package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which can clutter the npm registry and mislead developers into using potentially harmful packages. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards.

How To Fix

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

npm uninstall rino-poke4

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-poke4 package and monitor your project for any unintended dependencies that may have been introduced. Regularly audit your package-lock.json file to ensure no malicious packages are present.

Conclusion

The rino-poke4 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and repopulates the registry with harmful variants. It is essential to remove this package from your projects and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for rino-poke4 →

Share this vulnerability

FAQ

rino-poke4 is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its integrity and security.

You should uninstall the package immediately using the command 'npm uninstall rino-poke4' and check for any dependencies that may have been affected.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

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-poke4

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