Critical Malicious Code Vulnerability in magento-coding-standard-eslint-plugin

Summary

27/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-522: Malicious code in magento-coding-standard-eslint-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The magento-coding-standard-eslint-plugin is an npm package designed to enforce coding standards for Magento projects using ESLint. It helps developers maintain code quality and consistency. However, this package 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 discovery of embedded malicious code within the magento-coding-standard-eslint-plugin package. This code can lead to full system compromise, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code poses significant risks, as it may not be fully eradicated even after the package is removed, leaving systems vulnerable to further exploitation.

How To Fix

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

npm uninstall magento-coding-standard-eslint-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

As a workaround, consider using alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your development environment is secure and monitor for any unusual activity.

Conclusion

The discovery of malicious code in the magento-coding-standard-eslint-plugin poses a serious threat to systems using this package. Immediate action is required to remove the package and secure any compromised information. Utilizing tools like Vulert can help prevent future vulnerabilities and ensure the safety of your development environment.

See every vulnerability recorded for magento-coding-standard-eslint-plugin →

Share this vulnerability

FAQ

Immediately remove the magento-coding-standard-eslint-plugin package and rotate any sensitive information that may have been compromised.

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

Leaving the package installed can lead to unauthorized access to your system, potentially compromising sensitive data and allowing further exploitation.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security updates for the packages you use.

While many npm packages are safe, it is essential to verify the credibility of packages and monitor for vulnerabilities, as malicious packages can occasionally be published.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall magento-coding-standard-eslint-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