Malicious Code Injection in rinto-poke59: A Threat to npm Packages

rinto-poke59 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164833: Malicious code in rinto-poke59 (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-poke59 is an npm package that was part of a token reward campaign associated with the tea.xyz protocol. 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-poke59 stems from its inclusion in a series of malicious packages that automatically generate and publish derivative packages with randomized names. These packages are designed to inflate developer reputation scores for token rewards. The malicious code modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to pollution of the npm registry and potential security risks for users relying on these packages.

How To Fix

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

npm uninstall rinto-poke59

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 measure, you can avoid using the rinto-poke59 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and source of packages before including them in your project.

Conclusion

The rinto-poke59 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages. Regular monitoring and updates can help maintain the security of your applications.

See every vulnerability recorded for rinto-poke59 →

Share this vulnerability

FAQ

rinto-poke59 is an npm package that was part of a malicious campaign to inflate developer reputation scores for token rewards.

The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application and compromising its security.

You should uninstall the package immediately using the command npm uninstall rinto-poke59 and review your project's dependencies for any other potentially malicious packages.

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

Yes, you should look for well-reviewed and actively maintained packages that provide similar functionality but do not have a history of malicious activity.

How To Fix

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

npm uninstall rinto-poke59

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