Malicious Code Injection in umi-sate44-breki: A Threat to npm Ecosystem

umi-sate44-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75881: Malicious code in umi-sate44-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 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 package umi-sate44-breki is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, thereby posing a significant risk to developers and their projects.

Vulnerability Detail

The vulnerability in umi-sate44-breki originates from its association with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative versions with randomized names, effectively polluting the npm registry. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to reputation inflation for malicious actors and compromise the integrity of the npm ecosystem.

How To Fix

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

npm uninstall umi-sate44-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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package and avoiding similar packages that may be part of the malicious campaign.

Conclusion

The umi-sate44-breki package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. Immediate action is required to remove this package and safeguard your projects from potential threats. Regular monitoring and updates are essential to maintain the security of your software.

See every vulnerability recorded for umi-sate44-breki →

Share this vulnerability

FAQ

umi-sate44-breki is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

The vulnerability can lead to the introduction of malicious code in your application, potentially compromising its security and integrity.

You should immediately uninstall the package using 'npm uninstall umi-sate44-breki' and check your application for any signs of compromise.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Yes, there are several packages associated with the tea.xyz token reward campaign that may also pose similar risks. It is advisable to review your dependencies regularly.

How To Fix

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

npm uninstall umi-sate44-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