Malicious Code Vulnerability in rinto-poke121: Exploitation of npm Registry

rinto-poke121 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164776: Malicious code in rinto-poke121 (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-poke121 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. It is designed to facilitate the distribution of rewards through the npm ecosystem. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in rinto-poke121 arises from its inclusion in a campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores for token rewards but also modifies the package.json file to remove private flags and alters version numbers. The continuous republishing of these variants leads to pollution of the npm registry, making it difficult for developers to trust the integrity of packages.

How To Fix

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

npm uninstall rinto-poke121

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 the rinto-poke121 package and any packages that depend on it. Regularly monitor your package dependencies and remove any that are identified as malicious.

Conclusion

The rinto-poke121 package has been identified as a malicious entity within the npm ecosystem, capable of compromising package integrity and developer trust. Immediate action is required to remove this package and safeguard your projects from potential risks. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for rinto-poke121 →

Share this vulnerability

FAQ

rinto-poke121 is an npm package involved in a token reward campaign that has been flagged for containing malicious code.

The vulnerability can lead to the pollution of the npm registry, making it difficult to trust other packages and potentially exposing your project to further security risks.

You should uninstall the package immediately using npm uninstall rinto-poke121 and check for any affected dependencies.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

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 rinto-poke121

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