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

rino-poke57 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164704: Malicious code in rino-poke57 (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-poke57 is an npm package that appears to be part of a larger campaign aimed at exploiting the npm registry. This package is designed to facilitate token reward schemes by generating and publishing numerous derivative packages with randomized names. Its functionality is compromised due to the presence of malicious code that alters package metadata and floods the registry with unwanted variants.

Vulnerability Detail

The vulnerability in rino-poke57 stems from its association with the tea.xyz token reward campaign, which has been identified as a source of malicious npm packages. The malicious code modifies the package.json file to remove private flags, changes version numbers, and generates random package names, leading to the pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may 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-poke57

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-poke57 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies using tools like npm audit.

Conclusion

The rino-poke57 package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for rino-poke57 →

Share this vulnerability

FAQ

rino-poke57 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code alters package metadata, potentially leading to the use of compromised packages and affecting the integrity of your project.

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

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall rino-poke57

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