Malicious Code Injection in milraoa-miopa-muiop Package - npm Vulnerability

milraoa-miopa-muiop Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160454: Malicious code in milraoa-miopa-muiop (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 milraoa-miopa-muiop package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the milraoa-miopa-muiop package, which is associated with the tea.xyz token reward campaign. This code includes scripts that automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to registry pollution and potential exploitation by attackers.

How To Fix

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

npm uninstall milraoa-miopa-muiop

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 milraoa-miopa-muiop package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The milraoa-miopa-muiop package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and applications. It is crucial to remove this package and monitor your dependencies to maintain the security of your projects.

See every vulnerability recorded for milraoa-miopa-muiop →

Share this vulnerability

FAQ

The milraoa-miopa-muiop package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

This vulnerability can lead to the pollution of the npm registry and may expose your application to further security risks if malicious packages are inadvertently included.

If you have installed the milraoa-miopa-muiop package, you should uninstall it immediately and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which allows you to monitor your package-lock.json file for vulnerabilities without requiring access to your code or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall milraoa-miopa-muiop

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