Which versions of ethersnode are malicious?

The following npm versions of ethersnode are flagged malicious: 1.2.0, 1.3.0. Treat any of these as compromised.

How do I remediate ethersnode if I installed it?

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

If ethersnode 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 ethersnode part of a known attack campaign?

Yes — ethersnode is associated with the GHSA-g45j-72gf-5658, RLMA-2026-01300, RLUA-2026-01760 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 ethersnode 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 ethersnode (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethersnode across your stack and pipelines.

Malicious package

ethersnodenpm

Malicious code in ethersnode (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1174

Immediate action

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

npm uninstall ethersnode

What this malware does

The package ethersnode 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.

Malicious versions

2 flagged

1.2.01.3.0

Indicators of compromise (SHA-256)

839839d225447c7bde56628923d8e812808862fdda069eb93df578a04cc25525

05646d5daf39bd4f36dd32267c3f5428b8eeb3913781b2c8549594679dafac3b

0fcbfeb54ac7c6165a02587360633afc87255d844b8fb26c8ce09a3a54520319

b1aa7e45d17d775f54082df1e1b79819309cd1bc7cbe234ba9d785aa5a16f698

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 ethersnode (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethersnode across your stack and pipelines.
If you installed it — respond
Remove ethersnode 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 ethersnode 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 ethersnode 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. ethersnode on npm has been identified as a malicious package (versions 1.2.0, 1.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g45j-72gf-5658RLMA-2026-01300RLUA-2026-01760

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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