Critical Malicious Code Vulnerability in eslint-verify-plugin

eslint-verify-plugin Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1173: Malicious code in eslint-verify-plugin (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

eslint-verify-plugin is an npm package designed to enhance the functionality of ESLint, a widely used tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. This plugin allows developers to create custom rules and improve code quality. However, it has been found to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the eslint-verify-plugin package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The presence of this malicious code poses a significant risk, as it may lead to data breaches and unauthorized control over the affected systems.

How To Fix

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

npm uninstall eslint-verify-plugin

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

There are no effective workarounds for this vulnerability other than removing the package and ensuring that all sensitive data is secured. It is essential to monitor your system for any signs of unauthorized access.

Conclusion

The discovery of malicious code in the eslint-verify-plugin poses a serious threat to users and their systems. Immediate action is required to mitigate the risks associated with this vulnerability. Users should remove the package, rotate sensitive information, and monitor their systems for any signs of compromise.

See every vulnerability recorded for eslint-verify-plugin →

Share this vulnerability

FAQ

eslint-verify-plugin is an npm package that extends ESLint's capabilities by allowing developers to create custom linting rules for JavaScript code.

The malicious code can compromise your system, allowing attackers to gain unauthorized access to sensitive information and potentially control your computer.

Immediately remove the eslint-verify-plugin package and rotate any secrets or keys stored on the affected system.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without needing to sign up.

While removing the package is essential, there is no guarantee that all malicious software has been removed. It is advisable to conduct a thorough security audit of your system.

How To Fix

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

npm uninstall eslint-verify-plugin

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