Malicious Code Vulnerability in ether-lint: npm Package Compromised

ether-lint Updated 20 Feb 2026

Summary

12/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-941: Malicious code in ether-lint (npm). Affects ether-lint versions 5.9.1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

ether-lint is an npm package designed to assist developers in linting their Ethereum smart contracts. It provides tools for analyzing and improving the quality of smart contract code. However, version 5.9.1 of ether-lint has been identified as malicious, executing commands that can lead to harmful outcomes for users.

Vulnerability Detail

The vulnerability in ether-lint stems from its malicious behavior, where the package executes one or more commands associated with harmful actions. This can lead to unauthorized access, data breaches, or system compromise. The issue was identified by the OpenSSF Package Analysis project, which flagged the package as malicious due to its potential to execute harmful commands on the user's system.

How To Fix

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

npm uninstall ether-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

As a temporary workaround, users can avoid using ether-lint version 5.9.1 and instead utilize alternative linting tools for Ethereum smart contracts until a secure version is confirmed.

Conclusion

The ether-lint package version 5.9.1 has been flagged as malicious due to its ability to execute harmful commands. Users are advised to update to a secure version or use alternative tools for linting their Ethereum smart contracts to mitigate risks associated with this vulnerability.

See every vulnerability recorded for ether-lint →

Share this vulnerability

FAQ

ether-lint is an npm package that helps developers lint and analyze Ethereum smart contracts to improve code quality.

A malicious package is one that executes harmful commands or actions that can compromise the user's system or data.

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

You should uninstall ether-lint version 5.9.1 immediately and install a different version that is not compromised.

Yes, there are several alternative tools available, such as Solhint and MythX, which can be used for linting and analyzing smart contracts.

How To Fix

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

npm uninstall ether-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