Critical Malicious Code Vulnerability in eslint-config-zoo Package

eslint-config-zoo Updated 12 Dec 2025

Summary

12/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192558: Malicious code in eslint-config-zoo (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-config-zoo is an npm package designed to provide a set of ESLint configurations for JavaScript projects. It helps developers maintain code quality and consistency by enforcing coding standards. However, the package has been compromised, leading to a serious security vulnerability that can fully compromise any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the eslint-config-zoo package. This code can grant unauthorized access to the system, allowing attackers to control the machine and potentially exfiltrate sensitive data. The malicious nature of this code has been confirmed by security researchers, and any system running this package should be considered at risk. Users are advised to take immediate action to mitigate the threat.

How To Fix

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

npm uninstall eslint-config-zoo

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 still need ESLint configurations, consider using an alternative package that is known to be secure. You can search for other ESLint configuration packages on npm and choose one that fits your project's needs.

Conclusion

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

See every vulnerability recorded for eslint-config-zoo →

Share this vulnerability

FAQ

You should immediately uninstall the package using 'npm uninstall eslint-config-zoo' and rotate any sensitive credentials stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

No, there is currently no patched version available. The only solution is to remove the package entirely.

Failing to address this vulnerability can lead to full system compromise, unauthorized access to sensitive data, and potential data breaches.

Yes, you can use other ESLint configuration packages that are secure and do not contain malicious code.

How To Fix

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

npm uninstall eslint-config-zoo

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