Malicious Code Injection in rinto-poke120: A Threat to npm Users

rinto-poke120 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164775: Malicious code in rinto-poke120 (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-poke120 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards through various scripts. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use or depend on this compromised package.

Vulnerability Detail

The vulnerability in rinto-poke120 stems from its inclusion in a campaign that generates and publishes numerous derivative packages with altered metadata. The malicious code modifies the package.json file to remove private flags, changes version numbers, and creates random package names, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may lead to security breaches or loss of reputation.

How To Fix

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

npm uninstall rinto-poke120

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 rinto-poke120 and any packages that depend on it. Additionally, consider using the following command to uninstall the package: npm uninstall rinto-poke120.

Conclusion

The rinto-poke120 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for rinto-poke120 →

Share this vulnerability

FAQ

rinto-poke120 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to the inclusion of compromised packages in your project, potentially exposing your application to security risks.

You should uninstall the package immediately and check for any dependencies that may also be affected.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

How To Fix

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

npm uninstall rinto-poke120

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