Malicious Code Exploit in milisa-migaop-miodsdut Package: A Threat to npm Users

milisa-migaop-miodsdut Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160431: Malicious code in milisa-migaop-miodsdut (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 milisa-migaop-miodsdut package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is linked to a token reward campaign that has been associated with malicious activities, including the automatic generation of derivative packages to inflate developer reputation scores. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the milisa-migaop-miodsdut package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to continuously republish variants with randomized names, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such malicious packages.

How To Fix

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

npm uninstall milisa-migaop-miodsdut

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, users can avoid using the milisa-migaop-miodsdut package until a secure version is released. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The milisa-migaop-miodsdut package is compromised by malicious code that poses significant risks to developers using it. It is crucial to update or remove the package and utilize monitoring tools like Vulert to ensure the security of your applications. Awareness and proactive measures are essential in mitigating the impact of such vulnerabilities.

See every vulnerability recorded for milisa-migaop-miodsdut →

Share this vulnerability

FAQ

It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

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

You should immediately update the package to the latest version or remove it from your project to mitigate any risks.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall milisa-migaop-miodsdut

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