Which versions of @ensdomains/address-encoder are malicious?

The following npm versions of @ensdomains/address-encoder are flagged malicious: 1.1.5. Treat any of these as compromised.

How do I remediate @ensdomains/address-encoder if I installed it?

@ensdomains/address-encoder is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @ensdomains/address-encoder — how do I know if it already compromised me?

If @ensdomains/address-encoder 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 @ensdomains/address-encoder part of a known attack campaign?

Yes — @ensdomains/address-encoder is associated with the GHSA-6gpw-2wh2-2xcm 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 @ensdomains/address-encoder 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 @ensdomains/address-encoder (version 1.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/address-encoder across your stack and pipelines.

Malicious package

@ensdomains/address-encodernpm

Malicious code in @ensdomains/address-encoder (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190665

Immediate action

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

npm uninstall @ensdomains/address-encoder

What this malware does

The package @ensdomains/address-encoder 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.1.5

Indicators of compromise (SHA-256)

0055d835684d30fef39b594e10ca55c8313c0540ab9dbbbe76e3e539ef25eede

ec8264ecb2af0b5028f08af1a108f7fe73cd1cbe55ea2cb7102a3e28b2e1052e

1b64d83b623974e5dcd650b6ee4c067d063046fa692e27883ebf5d9935714c13

85053bc57267d919ff30f906ec6c9cb691e17f17b5b887913d35733b4caff122

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ensdomains/address-encoder (version 1.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/address-encoder across your stack and pipelines.
If you installed it — respond
@ensdomains/address-encoder is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @ensdomains/address-encoder 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 @ensdomains/address-encoder 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. @ensdomains/address-encoder on npm has been identified as a malicious package (version 1.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6gpw-2wh2-2xcm

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ensdomains/address-encoder-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring