Malicious Code Injection in rino-poke29: A Threat to npm Packages

rino-poke29 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164673: Malicious code in rino-poke29 (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-poke29 is an npm package that is part of a broader campaign aimed at exploiting the npm registry. This package, like others in the tea.xyz token reward initiative, is designed to manipulate the npm ecosystem by generating and publishing numerous derivative packages. Its functionality is compromised due to the presence of malicious scripts that alter package metadata, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in rino-poke29 stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for legitimate packages to be discovered and used. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit npm's publishing mechanisms.

How To Fix

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

npm uninstall rino-poke29

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-poke29 package and consider using alternative packages that provide similar functionality without the associated risks. Monitor your package dependencies regularly to ensure that no malicious packages are included.

Conclusion

The rino-poke29 package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for rino-poke29 →

Share this vulnerability

FAQ

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

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

You should uninstall the package immediately using npm uninstall rino-poke29 and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Yes, consider using alternative packages that are well-reviewed and have a strong reputation in the community. Always verify the source before installation.

How To Fix

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

npm uninstall rino-poke29

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