Which versions of @ensdomains/unruggable-gateways are malicious?

The following npm versions of @ensdomains/unruggable-gateways are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate @ensdomains/unruggable-gateways if I installed it?

@ensdomains/unruggable-gateways 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/unruggable-gateways — how do I know if it already compromised me?

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

Yes — @ensdomains/unruggable-gateways is associated with the GHSA-g6xr-xj9x-wq24 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/unruggable-gateways 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/unruggable-gateways (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/unruggable-gateways across your stack and pipelines.

Malicious package

@ensdomains/unruggable-gatewaysnpm

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

MAL-2025-190814

Immediate action

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

npm uninstall @ensdomains/unruggable-gateways

What this malware does

The package @ensdomains/unruggable-gateways 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

0.0.3

Indicators of compromise (SHA-256)

4a45578512742a5af3948e9d05ac6d815e456d83b22e1ec407be2e13f69e78ae

19161096da8bc9f3514ff35b262f9d1f1683b0f54a01041afb0993d5d5268f9e

12663867673b1e44bbbd266dec685c6654a0478079e2b54f86bd28f67ebca8ef

e19d1ca68465698006dac5a535311d2a392e6e624618310034606ef4b0345106

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

Campaign

GHSA-g6xr-xj9x-wq24

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ensdomains/unruggable-gateways-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