Which versions of etherres are malicious?

The following npm versions of etherres are flagged malicious: 6.15.0. Treat any of these as compromised.

How do I remediate etherres if I installed it?

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

If etherres 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.

Is etherres part of a known attack campaign?

Yes — etherres is associated with the RLMA-2025-04517, RLUA-2025-05790 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 etherres across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for etherres (version 6.15.0).

Malicious package

etherresnpm

Advisory published Aug 14, 2025Updated Dec 2, 2025

etherres is a confirmed malicious npm package (MAL-2025-19891) that executes malicious code on install (malicious version 6.15.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in etherres (npm)

MAL-2025-19891

Immediate action

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

npm uninstall etherres

What this malware does

The package etherres was found to contain malicious code.

Malicious versions

1 flagged

6.15.0

Indicators of compromise (SHA-256)

7bbb431a2fceb42e01e40ab0108605c2b3391b7eb49b3d5e43b0b8b9bbe3beb5

034d70113554d02b7eac74bdba44ec4e0d271c688587413bec3f1292059e738d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for etherres (version 6.15.0).
If you installed it — respond
Remove etherres 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 etherres 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. etherres on npm has been identified as a malicious package (version 6.15.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04517RLUA-2025-05790

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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