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

rinto-poke60 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164835: Malicious code in rinto-poke60 (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-poke60 is an npm package that is part of a larger campaign exploiting the npm registry. It is designed to facilitate token rewards for the tea.xyz protocol. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior, leading to potential security risks for users and developers relying on it.

Vulnerability Detail

The vulnerability in rinto-poke60 stems from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, resulting in the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of reputation.

How To Fix

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

npm uninstall rinto-poke60

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-poke60 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The rinto-poke60 package poses a significant security risk due to its malicious code injection. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to protect their projects. By uninstalling the affected package and utilizing monitoring tools like Vulert, developers can safeguard their applications from potential threats.

See every vulnerability recorded for rinto-poke60 →

Share this vulnerability

FAQ

rinto-poke60 is an npm package involved in a malicious campaign that aims to exploit the npm registry for token rewards.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.

You should uninstall the package immediately using the command: npm uninstall rinto-poke60.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your dependencies, use trusted packages, and monitor your projects for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall rinto-poke60

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