Malicious Code Injection in rinto-poke112: A Threat to npm Ecosystem

rinto-poke112 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164766: Malicious code in rinto-poke112 (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

rinto-poke112 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various automated scripts. However, it has been identified as containing malicious code that compromises the integrity of the npm registry by generating and publishing derivative packages with randomized names, ultimately inflating developer reputation scores.

Vulnerability Detail

The vulnerability in rinto-poke112 originates from its association with the tea.xyz token reward campaign. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall rinto-poke112

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, you can avoid using the rinto-poke112 package and monitor your package-lock.json file for any unauthorized changes. Regularly audit your npm packages using the command 'npm audit' to identify and address vulnerabilities.

Conclusion

The rinto-poke112 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry with compromised packages. It is essential to take immediate action by uninstalling this package and monitoring your dependencies for vulnerabilities.

See every vulnerability recorded for rinto-poke112 →

Share this vulnerability

FAQ

rinto-poke112 is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

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

You should uninstall the rinto-poke112 package immediately using 'npm uninstall rinto-poke112' and audit your project for any other vulnerabilities.

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

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.

How To Fix

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

npm uninstall rinto-poke112

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