Malicious Code Injection in nina-bubur47-miaww: A Threat to npm Users

nina-bubur47-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88778: Malicious code in nina-bubur47-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 Penetration testing for web, API and mobile 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 'nina-bubur47-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 the presence of malicious code that alters package metadata.

Vulnerability Detail

The vulnerability in 'nina-bubur47-miaww' originates from its malicious payload, which modifies the package.json file by removing private flags and changing version numbers. It generates random Indonesian-themed package names and continuously republishes these variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially exposing their applications to further security risks.

How To Fix

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

npm uninstall nina-bubur47-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 'nina-bubur47-miaww' package and instead 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 'nina-bubur47-miaww' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies to avoid potential security threats.

See every vulnerability recorded for nina-bubur47-miaww →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that alters package metadata and floods the npm registry with compromised packages.

You can use Vulert to monitor your package-lock.json file for vulnerabilities. The Vulert playground allows you to check for affected packages without any signup.

You should uninstall the package immediately using 'npm uninstall nina-bubur47-miaww' and look for alternatives.

Yes, using compromised packages can lead to security vulnerabilities in your application, including data breaches and unauthorized access.

Regularly monitor your dependencies using tools like Vulert, keep your packages updated, and review package sources before installation.

How To Fix

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

npm uninstall nina-bubur47-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