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

rinto-poke108 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164761: Malicious code in rinto-poke108 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

rinto-poke108 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. Its functionality is compromised due to the presence of malicious scripts that alter package metadata and republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability in rinto-poke108 stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only inflates developer reputation scores fraudulently but also poses a risk of dependency confusion and potential exploitation by other malicious actors. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.

How To Fix

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

npm uninstall rinto-poke108

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-poke108 package and any other packages that may have been published as part of the same malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks associated with malicious packages.

Conclusion

The rinto-poke108 package represents a significant threat to the npm ecosystem due to its malicious behavior of altering package metadata and republishing variants. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove any affected packages to safeguard your projects.

See every vulnerability recorded for rinto-poke108 →

Share this vulnerability

FAQ

rinto-poke108 is an npm package identified as part of a malicious campaign that modifies package metadata and republish variants to inflate developer reputation scores.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Using rinto-poke108 can lead to dependency confusion, pollution of the npm registry, and potential exploitation by malicious actors due to the altered package metadata.

You should uninstall the rinto-poke108 package immediately using the command npm uninstall rinto-poke108 and audit your dependencies for any other malicious packages.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem to mitigate risks.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall rinto-poke108

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