Malicious Code Vulnerability in metro-evaluator Package

metro-evaluator Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1792: Malicious code in metro-evaluator (npm). Affects metro-evaluator versions 1.0.0 – 1.0.3. 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 metro-evaluator package is a tool used in the Node.js ecosystem, primarily for evaluating Metro configurations in React Native applications. It offers developers a streamlined way to manage and optimize their Metro bundler settings. However, certain versions of this package have been found to contain malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability identified in the metro-evaluator package involves the presence of malicious code that can compromise the integrity of applications using this package. This issue originates from specific versions (1.0.0 to 1.0.3) that were tampered with, allowing attackers to execute arbitrary code within the context of the application. The ramifications of this vulnerability can include unauthorized access to sensitive data, data corruption, and potential system compromise.

How To Fix

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

npm uninstall metro-evaluator

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 remove the metro-evaluator package from your project if it is not essential. To do this, run the following command: npm uninstall metro-evaluator. Alternatively, consider using an alternative package that provides similar functionality without the associated risks.

Conclusion

The metro-evaluator package has been identified as containing malicious code in specific versions, posing a significant risk to applications. It is essential for developers to update to a secure version or consider alternative solutions to mitigate these risks. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application security.

See every vulnerability recorded for metro-evaluator →

Share this vulnerability

FAQ

Versions 1.0.0, 1.0.1, 1.0.2, and 1.0.3 of the metro-evaluator package are known to contain malicious code.

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

If immediate updates are not possible, consider removing the metro-evaluator package or using an alternative package until a secure version is available.

Using the affected versions can lead to unauthorized access to sensitive data, data corruption, and potential system compromise, which can severely impact your application's security.

How To Fix

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

npm uninstall metro-evaluator

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