Malicious Code Injection in rino-poke27: npm Package Vulnerability

rino-poke27 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164671: Malicious code in rino-poke27 (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-poke27 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been compromised to include malicious scripts that manipulate its functionality and affect the npm ecosystem.

Vulnerability Detail

The vulnerability in rino-poke27 originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, potentially affecting developers' reputation scores and introducing security risks into projects that depend on these packages.

How To Fix

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

npm uninstall rino-poke27

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 rino-poke27 and replace it with a trusted alternative. Additionally, you can monitor your package dependencies using tools like Vulert, which provides real-time alerts for open-source vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The rino-poke27 package has been identified as containing malicious code that can compromise the integrity of the npm registry and affect developers' projects. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate risks associated with open-source software.

See every vulnerability recorded for rino-poke27 →

Share this vulnerability

FAQ

rino-poke27 is an npm package involved in the tea.xyz token reward campaign, which has been compromised to include malicious code.

The vulnerability can lead to the pollution of the npm registry, affecting the integrity of your project and potentially introducing security risks.

You should uninstall the rino-poke27 package immediately using 'npm uninstall rino-poke27' and replace it with a trusted alternative.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities and alerts you in real-time.

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

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