Critical Malicious Code Vulnerability in @mailpoet/eslint-config Package

@mailpoet/eslint-config Updated 22 Jan 2026

Summary

22/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-456: Malicious code in @mailpoet/eslint-config (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 @mailpoet/eslint-config package is a configuration tool for ESLint, a widely used JavaScript linting utility that helps developers maintain code quality by identifying and reporting on patterns found in ECMAScript/JavaScript code. This package is intended to streamline the setup of ESLint with predefined rules and settings. However, it has been found to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @mailpoet/eslint-config package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The origin of this vulnerability is linked to the package being flagged as malicious by security researchers, indicating that it poses a significant risk to users and their systems.

How To Fix

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

npm uninstall @mailpoet/eslint-config

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 workaround, if you need to maintain ESLint functionality, consider using an alternative ESLint configuration package that is known to be secure. You can install a different package by running: 'npm install eslint-config-standard'.

Conclusion

The @mailpoet/eslint-config package has been identified as containing malicious code that poses a serious security risk. Users are advised to uninstall the package immediately and take necessary precautions to secure their systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @mailpoet/eslint-config →

Share this vulnerability

FAQ

The malicious code can compromise the entire system, allowing unauthorized access to sensitive data.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Immediately uninstall the package and rotate any sensitive information stored on the affected system.

Currently, there is no patched version available for this package.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and only install packages from trusted sources.

How To Fix

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

npm uninstall @mailpoet/eslint-config

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