Which versions of ethers-lint are malicious?

The following npm versions of ethers-lint are flagged malicious: 5.8.1. Treat any of these as compromised.

How do I remediate ethers-lint if I installed it?

Remove ethers-lint from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed ethers-lint — how do I know if it already compromised me?

If ethers-lint was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find ethers-lint across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ethers-lint (version 5.8.1).

Malicious package

ethers-lintnpm

Advisory published Feb 5, 2026Updated Feb 6, 2026

ethers-lint is a confirmed malicious npm package (MAL-2026-773) that executes malicious code on install (malicious version 5.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ethers-lint (npm)

MAL-2026-773

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ethers-lint

What this malware does

The package ethers-lint was found to contain malicious code.

The OpenSSF Package Analysis project identified 'ethers-lint' @ 5.8.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

5.8.1

Indicators of compromise (SHA-256)

d8dbb4e1fc55b2c8ea0ae2b784f605750cd1a716e7444e12ee3a8de162063f04

315365a10d9e3322792c18bdb8c5a8e620bbcc2a9ad8d5a1d5ef139ef6e47777

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ethers-lint (version 5.8.1).
If you installed it — respond
Remove ethers-lint from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ethers-lint was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ethers-lint on npm has been identified as a malicious package (version 5.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks ethers-lint-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database