Malicious Code Injection in umi-bubur68-miaww: A Threat to npm Packages

umi-bubur68-miaww Updated 19 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-117612: Malicious code in umi-bubur68-miaww (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 package 'umi-bubur68-miaww' is part of a broader campaign targeting npm, where malicious packages are created to inflate developer reputation scores for token rewards. These packages often contain scripts that automate the generation and publication of derivative packages with randomized names, compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'umi-bubur68-miaww' stems from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other projects that depend on npm packages.

How To Fix

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

npm uninstall umi-bubur68-miaww

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-bubur68-miaww' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any unauthorized changes.

Conclusion

The 'umi-bubur68-miaww' package poses significant risks due to its malicious code designed to manipulate npm packages. It is crucial to remove this package from your projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for umi-bubur68-miaww →

Share this vulnerability

FAQ

The main risk is that it can modify your project's package.json file, leading to unauthorized changes and potential security vulnerabilities.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should uninstall the package immediately using 'npm uninstall umi-bubur68-miaww' and check for any other dependencies that may be affected.

Yes, you should look for reputable packages that offer similar functionality without the risks associated with malicious packages.

Vulert monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file, ensuring your applications remain secure.

How To Fix

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

npm uninstall umi-bubur68-miaww

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