Malicious Code Injection in indah-toge70-ruro Package

indah-toge70-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104138: Malicious code in indah-toge70-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The indah-toge70-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, making them a target for malicious activities.

Vulnerability Detail

The vulnerability in the indah-toge70-ruro package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit the npm registry by polluting it with numerous derivative packages. The ramifications include potential security risks for developers who unknowingly install these packages, as they may inadvertently contribute to the malicious activity.

How To Fix

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

npm uninstall indah-toge70-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 avoid using the indah-toge70-ruro package and instead look for alternative packages that provide similar functionality without the associated risks. Always review package details and community feedback before installation.

Conclusion

The indah-toge70-ruro package poses a significant security risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any known vulnerabilities. Regular monitoring and updates can help maintain the security of your projects.

See every vulnerability recorded for indah-toge70-ruro →

Share this vulnerability

FAQ

The indah-toge70-ruro package is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the installation of malicious code that modifies your project's package.json, potentially compromising your application's security.

You should uninstall the indah-toge70-ruro package immediately using the command npm uninstall indah-toge70-ruro.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, 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 indah-toge70-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