Malicious Code Injection in ida-toge11-ruro Package

ida-toge11-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103917: Malicious code in ida-toge11-ruro (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The ida-toge11-ruro package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the ida-toge11-ruro package stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to continuously republish variants of the package, polluting the npm registry and potentially compromising the security of applications that depend on it. The origin of this vulnerability is linked to a broader campaign that exploits npm's publishing mechanisms for token rewards.

How To Fix

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

npm uninstall ida-toge11-ruro

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 prevent the installation of the ida-toge11-ruro package by using npm's package-lock.json file to lock down your dependencies. Ensure that your project does not include this package by removing it from your package.json and running npm install to update your lock file.

Conclusion

The ida-toge11-ruro package poses a significant security risk due to its malicious code that alters package metadata and republish behavior. It is essential to remove this package from your dependencies and monitor your project for vulnerabilities using tools like Vulert to maintain the integrity of your applications.

See every vulnerability recorded for ida-toge11-ruro →

Share this vulnerability

FAQ

The ida-toge11-ruro package is an npm package associated with a token reward campaign that has been identified as malicious.

The malicious code modifies your package.json file, potentially exposing your application to security risks and polluting the npm registry.

You should remove the ida-toge11-ruro package from your project and update your dependencies to ensure your application is secure.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall ida-toge11-ruro

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