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

rino-poke43 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164689: Malicious code in rino-poke43 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

rino-poke43 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 package metadata and republish variants to inflate developer reputation scores, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in rino-poke43 originates from its association with the tea.xyz token reward campaign. The package includes malicious scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of the ecosystem and affecting developers relying on these packages.

How To Fix

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

npm uninstall rino-poke43

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-poke43 package and replace it with a verified alternative. Always verify the source of any npm package before installation.

Conclusion

The rino-poke43 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any identified vulnerabilities. Regular monitoring and updates can help maintain the security of your projects.

See every vulnerability recorded for rino-poke43 →

Share this vulnerability

FAQ

rino-poke43 is an npm package involved in the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to the injection of malicious code and the proliferation of unwanted packages, compromising the integrity of your project.

You should uninstall the package immediately using the command npm uninstall rino-poke43.

You can use tools like Vulert, which monitors your package-lock.json file for 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-poke43

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