Malicious Code Injection in umi-mieaceh99-breki Package

umi-mieaceh99-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75868: Malicious code in umi-mieaceh99-breki (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

The umi-mieaceh99-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the umi-mieaceh99-breki package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload is designed to continuously republish these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly use these compromised packages. The origin of this vulnerability is linked to a broader campaign that aims to manipulate the npm ecosystem for token rewards.

How To Fix

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

npm uninstall umi-mieaceh99-breki

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 umi-mieaceh99-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The umi-mieaceh99-breki package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. Immediate action is required to remove this package and prevent further exploitation. Utilizing tools like Vulert can enhance your project's security by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for umi-mieaceh99-breki →

Share this vulnerability

FAQ

The umi-mieaceh99-breki package is an npm package linked to a token reward campaign that automates the generation and publication of derivative packages.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially leading to security risks and pollution of the npm registry.

You should uninstall the umi-mieaceh99-breki package immediately using 'npm uninstall umi-mieaceh99-breki' to mitigate any risks.

Regularly audit your dependencies, use trusted packages, and consider utilizing tools like Vulert to monitor for vulnerabilities in your package-lock.json.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by vulnerabilities without needing to install anything.

How To Fix

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

npm uninstall umi-mieaceh99-breki

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