Which versions of ethers-jss are malicious?

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

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

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

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

Yes — ethers-jss is associated with the GHSA-xh65-7qcm-493w, RLMA-2026-05077, RLUA-2026-05533 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 ethers-jss 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 ethers-jss (version 6.13.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethers-jss across your stack and pipelines.

Malicious package

ethers-jssnpm

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

MAL-2026-5501

Immediate action

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

npm uninstall ethers-jss

What this malware does

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

1 flagged

6.13.1

Indicators of compromise (SHA-256)

56bf62c882d62bbb9bacc402f0f25f48e12b878ff454eda013fed56dc61db42e

b91924b328b819c4ceb53b2fbe8c534567286dc59865f1e893633747d79d4d9c

cc333fde438ccc89d8907d61a3d209065191144e1172b625742f333a1c52a54c

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

Campaign

GHSA-xh65-7qcm-493wRLMA-2026-05077RLUA-2026-05533

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ethers-jss-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