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

rinto-poke116 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164770: Malicious code in rinto-poke116 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

rinto-poke116 is an npm package that is part of a broader campaign exploiting the npm registry. It is designed to facilitate token rewards for the tea.xyz protocol. The package's primary function is to serve as a tool for developers, but it has been compromised to include malicious scripts that manipulate its own metadata and proliferate harmful variants.

Vulnerability Detail

The vulnerability in rinto-poke116 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, removing private flags and changing version numbers. The scripts generate random package names and continuously republish these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages.

How To Fix

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

npm uninstall rinto-poke116

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, avoid using rinto-poke116 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The rinto-poke116 package poses a significant threat due to its malicious code designed to manipulate npm registry data. Developers should take immediate action to remove this package and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for rinto-poke116 →

Share this vulnerability

FAQ

rinto-poke116 is an npm package that has been compromised to include malicious code as part of a campaign to inflate developer reputation scores.

Using rinto-poke116 can lead to security risks, including the potential for your project to be associated with malicious activities and the pollution of the npm registry.

You should uninstall the package immediately using 'npm uninstall rinto-poke116' and check your project for any other compromised packages.

You can use tools like npm audit or Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability 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-poke116

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