Critical Malicious Code Vulnerability in milla-migration Package

milla-migration Updated 23 Mar 2026

Summary

23/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2089: Malicious code in milla-migration (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 milla-migration package is an npm library designed for managing migrations in JavaScript applications. It provides developers with tools to create, execute, and manage database schema changes efficiently. However, this package has been compromised, embedding malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the milla-migration package, identified as GHSA-jvrr-w8mr-28hp. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The ramifications of this vulnerability are severe, as it may lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall milla-migration

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

Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package and securing your system.

Conclusion

The milla-migration package has been compromised with malicious code, posing significant security risks to affected systems. Immediate action is required to remove the package and secure sensitive information. Regular monitoring of dependencies is crucial to prevent future vulnerabilities.

See every vulnerability recorded for milla-migration →

Share this vulnerability

FAQ

You should immediately remove the milla-migration package and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Failing to address this vulnerability may result in unauthorized access to your system, data breaches, and potential loss of sensitive information.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

While most npm packages are safe, it is essential to remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

How To Fix

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

npm uninstall milla-migration

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