Malicious Code Detected in email-pattern Package - MAL-2025-19551

email-pattern Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19551: Malicious code in email-pattern (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The email-pattern package is an npm library designed to validate email formats using specific patterns. It is commonly used in web applications to ensure that user inputs conform to standard email formats. However, this package has been identified to contain malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the email-pattern package originates from the inclusion of malicious code that can compromise the security of applications using this library. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall email-pattern

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 email-pattern package and implement your own email validation logic using regular expressions or other libraries that are known to be secure. Here is a simple example of a regex-based email validation function:

function validateEmail(email) {
  const re = /^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$/;
  return re.test(String(email).toLowerCase());
}

Conclusion

The email-pattern package has been identified to contain malicious code that poses a significant threat to applications using it. It is crucial for developers to remove this package and consider secure alternatives to protect their applications from potential security breaches.

See every vulnerability recorded for email-pattern →

Share this vulnerability

FAQ

The email-pattern package is an npm library used for validating email formats in web applications.

The vulnerability involves the presence of malicious code that can compromise application security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

It is advised to remove the email-pattern package and replace it with a secure alternative or implement your own email validation logic.

Currently, there is no patched version available. It is best to remove the package until a secure alternative is found.

How To Fix

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

npm uninstall email-pattern

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