Malicious Code Injection in utomo-mieayam38-breki Package

utomo-mieayam38-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75921: Malicious code in utomo-mieayam38-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 utomo-mieayam38-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 for token rewards. However, its functionality has been compromised by malicious code that alters package metadata.

Vulnerability Detail

The vulnerability in the utomo-mieayam38-breki package stems from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to a broader campaign that aims to pollute the npm registry with derivative packages, potentially affecting the integrity and reliability of the npm ecosystem.

How To Fix

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

npm uninstall utomo-mieayam38-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 prevent the installation of this malicious package by adding it to your npm ignore list or by using a package manager that allows you to lock down your dependencies to known safe versions.

Conclusion

The utomo-mieayam38-breki package contains a significant vulnerability due to malicious code that alters package metadata. It is essential to remove this package and monitor your dependencies for any potential threats. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for utomo-mieayam38-breki →

Share this vulnerability

FAQ

The vulnerability can lead to the pollution of the npm registry with malicious packages, affecting the integrity of your project and potentially introducing security risks.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities. You can check your application against this vulnerability using the Vulert playground without any signup.

If you have installed the utomo-mieayam38-breki package, you should uninstall it immediately and review your project for any other potentially compromised packages.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software.

It is recommended to check for vulnerabilities regularly, especially after major updates or when new vulnerabilities are disclosed.

How To Fix

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

npm uninstall utomo-mieayam38-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