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

rinto-poke125 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164780: Malicious code in rinto-poke125 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The rinto-poke125 package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores. The presence of malicious scripts within this package poses a significant risk to users and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in rinto-poke125 originates from its association with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The malicious payload within rinto-poke125 modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the security of the affected package but also pollutes the npm registry with numerous derivative packages, potentially leading to reputation damage for developers and increased risk of exploitation.

How To Fix

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

npm uninstall rinto-poke125

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, users can avoid using the rinto-poke125 package altogether until a patched version is released. If the package is already in use, consider removing it from your project and replacing it with a secure alternative.

Conclusion

The rinto-poke125 package poses a significant security risk due to its malicious code that modifies essential project files and floods the npm registry. Users are strongly advised to update or remove this package to protect their projects and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for rinto-poke125 →

Share this vulnerability

FAQ

rinto-poke125 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.

You should update the package to a patched version or remove it from your project to mitigate the risk.

You can use tools like Vulert, which monitors your package-lock.json for open-source 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 any signup.

How To Fix

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

npm uninstall rinto-poke125

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