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

rinto-poke54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164828: Malicious code in rinto-poke54 (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-poke54 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various scripts that automatically generate and publish derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in rinto-poke54 stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially affecting other developers and users relying on legitimate packages.

How To Fix

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

npm uninstall rinto-poke54

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 remove the rinto-poke54 package from your project by executing: npm uninstall rinto-poke54. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The rinto-poke54 package has been identified as containing malicious code that compromises the npm registry. It is crucial for developers to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your projects.

See every vulnerability recorded for rinto-poke54 →

Share this vulnerability

FAQ

rinto-poke54 is an npm package associated with the tea.xyz token reward campaign, which aims to incentivize developers through token rewards.

The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and affecting the integrity of the npm registry.

You should uninstall the package immediately and monitor for any updates or patches that address the vulnerability.

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

You can find detailed information in the vulnerability report on the official npm registry or through security advisories related to the rinto-poke54 package.

How To Fix

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

npm uninstall rinto-poke54

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