Which versions of ether-lint are malicious?

The following npm versions of ether-lint are flagged malicious: 5.9.1, 5.9.4. Treat any of these as compromised.

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

Remove ether-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 ether-lint — how do I know if it already compromised me?

If ether-lint was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ether-lint part of a known attack campaign?

Yes — ether-lint is associated with the GHSA-9p23-x4p4-m392 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ether-lint (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ether-lint across your stack and pipelines.

Malicious package

ether-lintnpm

Malicious code in ether-lint (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-941

Immediate action

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

npm uninstall ether-lint

What this malware does

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

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

5.9.15.9.4

Indicators of compromise (SHA-256)

0b04121413aaf5e19353bf39b6f2f23a1c5ad03e92a48eaa23bf4162f258af8b

91fd63bfdad336609f23485d2ef2ac2140053efbfb31aa2bec1811be7139db95

08a3518c25a9f603c979dc178c89859aa6fceef5753fc19045904a84f08299ab

c8e14ef98aaca0dc035a27f9edd6286e29e73d16c2b4e7c98ab1afe1e4740e35

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ether-lint (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ether-lint across your stack and pipelines.
If you installed it — respond
Remove ether-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 ether-lint was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ether-lint before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-9p23-x4p4-m392

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks ether-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