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

rinto-poke7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164845: Malicious code in rinto-poke7 (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

rinto-poke7 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of software within the npm ecosystem. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the applications that depend on it.

Vulnerability Detail

The vulnerability in rinto-poke7 originates from its association with a campaign that floods npm with malicious packages. The package includes scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can inflate developer reputation scores fraudulently. The ramifications include potential security risks for applications relying on this package, as well as a degraded npm ecosystem.

How To Fix

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

npm uninstall rinto-poke7

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 workaround, you can prevent the installation of this malicious package by using the following command to uninstall it: npm uninstall rinto-poke7. Additionally, consider using npm audit to check for vulnerabilities in your project.

Conclusion

The rinto-poke7 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remain vigilant and remove such packages from their projects to maintain the integrity of their applications and the broader npm ecosystem.

See every vulnerability recorded for rinto-poke7 →

Share this vulnerability

FAQ

rinto-poke7 is an npm package that is part of a campaign to distribute software and reward developers with tokens. However, it has been identified as containing malicious code.

The vulnerability can lead to the modification of your package.json file and the introduction of malicious code, which can compromise your application's security.

You should uninstall the rinto-poke7 package immediately to mitigate any potential risks associated with its malicious code.

Currently, there is no patched version available for rinto-poke7. The best course of action is to remove the package from your project.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall rinto-poke7

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