Malicious Code Injection in indah-mieaceh22-tititugel Package

indah-mieaceh22-tititugel Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97924: Malicious code in indah-mieaceh22-tititugel (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-mieaceh22-tititugel package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. The malicious nature of this package lies in its ability to modify critical files, such as package.json, thereby compromising the integrity of projects that depend on it.

Vulnerability Detail

The vulnerability in the indah-mieaceh22-tititugel package originates from its malicious code that alters the package.json file by removing private flags and changing version numbers. This package is part of a broader scheme that floods the npm registry with numerous variants of itself, which can lead to pollution of the registry and potential security risks for developers who unknowingly install these packages. The presence of autopublish scripts further exacerbates the issue by automating the creation of these malicious packages.

How To Fix

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

npm uninstall indah-mieaceh22-tititugel

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-mieaceh22-tititugel package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The indah-mieaceh22-tititugel package contains malicious code that poses significant risks to developers and their projects. It is crucial to remove this package and any associated dependencies to maintain the security and integrity of your software. Regular monitoring and auditing of your dependencies can help prevent future vulnerabilities.

See every vulnerability recorded for indah-mieaceh22-tititugel →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can compromise your project's integrity by modifying critical files and introducing malicious code, which may lead to security risks.

You should uninstall the indah-mieaceh22-tititugel package immediately and check for any other affected packages in your project.

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

Absolutely! 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-mieaceh22-tititugel

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