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

umi-buburayam58-miaww Updated 19 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-117613: Malicious code in umi-buburayam58-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-buburayam58-miaww is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to malicious scripts that modify package metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the umi-buburayam58-miaww package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to a polluted npm registry, making it difficult for developers to find legitimate packages. The ramifications include potential security risks for applications relying on this package and a compromised developer reputation system.

How To Fix

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

npm uninstall umi-buburayam58-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 workaround, you can avoid using the affected package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The umi-buburayam58-miaww package poses a significant risk due to its malicious code that alters package metadata and republish variants. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for umi-buburayam58-miaww →

Share this vulnerability

FAQ

umi-buburayam58-miaww is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies package metadata and can lead to the pollution of the npm registry, posing security risks for applications that depend on this package.

You should uninstall the package immediately using the command: npm uninstall umi-buburayam58-miaww and check for any alternative packages.

You can use Vulert to monitor your project's dependencies for vulnerabilities in real-time. Simply upload your package-lock.json file to receive alerts.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.