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

rinto-poke43 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164815: Malicious code in rinto-poke43 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

rinto-poke43 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores through the creation and publication of derivative packages. Its functionality is compromised by the presence of malicious scripts that alter package metadata and publish numerous variants, leading to pollution of the npm ecosystem.

Vulnerability Detail

The vulnerability in rinto-poke43 stems from its association with the tea.xyz token reward campaign, which employs scripts to automatically generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, potentially leading to a polluted npm registry and undermining the integrity of the ecosystem. The origin of this vulnerability is linked to the exploitation of npm's publishing capabilities, allowing for the proliferation of harmful packages.

How To Fix

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

npm uninstall rinto-poke43

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, avoid using the rinto-poke43 package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to identify and remove any malicious packages.

Conclusion

The rinto-poke43 package poses a significant threat due to its malicious code designed to manipulate npm's publishing system. Users are advised to uninstall the package and monitor their projects for any dependencies that may include it. Utilizing tools like Vulert can help maintain the security of your open-source projects.

See every vulnerability recorded for rinto-poke43 →

Share this vulnerability

FAQ

rinto-poke43 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.

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

You should uninstall the package immediately using npm uninstall rinto-poke43 and check for any dependencies that may rely on it.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. The best course of action is to remove the package and monitor for any updates.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall rinto-poke43

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