Critical Malicious Code Vulnerability in expressjs-lint Package

expressjs-lint Updated 02 Mar 2026

Summary

02/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1106: Malicious code in expressjs-lint (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

The expressjs-lint package is a tool designed for linting Express.js applications, helping developers maintain code quality and adhere to best practices. It is commonly used in Node.js environments to ensure that code is clean and free of common errors. However, this package has been compromised, leading to severe security implications for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the expressjs-lint 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 malicious nature of the code has been confirmed by security researchers, and it poses a significant risk to the integrity and security of affected systems.

How To Fix

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

npm uninstall expressjs-lint

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 entirely. Ensure that you do not rely on expressjs-lint for linting your Express.js applications until a secure version is released.

Conclusion

The expressjs-lint package has been found to contain malicious code that poses a serious threat to any system using it. Immediate action is required to remove the package and secure any sensitive information. Stay vigilant and consider using tools like Vulert to monitor your applications for vulnerabilities.

See every vulnerability recorded for expressjs-lint →

Share this vulnerability

FAQ

expressjs-lint is a linting tool for Express.js applications that helps developers maintain code quality.

If expressjs-lint is installed, your system may be fully compromised, allowing attackers to access sensitive information.

You should uninstall the package immediately and rotate any sensitive information stored on the affected system.

Currently, there is no patched version available. It is recommended to remove the package until further notice.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall expressjs-lint

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