Malicious Code Vulnerability in rino-poke10: Exploitation of npm Registry

rino-poke10 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164642: Malicious code in rino-poke10 (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-poke10 is an npm package that is part of a broader token reward campaign associated with the tea.xyz protocol. This package, like many others in the campaign, is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in rino-poke10 stems from its malicious code, which is designed to remove private flags from package.json, alter version numbers, and generate random package names. This behavior is part of a larger scheme to exploit the npm registry by flooding it with derivative packages, which can lead to a loss of trust in the ecosystem and potential security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall rino-poke10

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-poke10 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure no malicious packages are included.

Conclusion

The rino-poke10 package contains malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor your dependencies to maintain a secure development environment. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.

See every vulnerability recorded for rino-poke10 →

Share this vulnerability

FAQ

rino-poke10 is an npm package involved in a token reward campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the modification of your package.json file, potentially exposing your project to security risks and affecting the integrity of your npm dependencies.

You should uninstall the rino-poke10 package immediately and check your project for any other compromised packages.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Always verify the source of packages before installation.

How To Fix

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

npm uninstall rino-poke10

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