Which versions of @ensdomains/solsha1 are malicious?

The following npm versions of @ensdomains/solsha1 are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate @ensdomains/solsha1 if I installed it?

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

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

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

Malicious package

@ensdomains/solsha1npm

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

MAL-2025-190737

Immediate action

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

npm uninstall @ensdomains/solsha1

What this malware does

The package @ensdomains/solsha1 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.4

Indicators of compromise (SHA-256)

48948aa2ba413f76c4fff56fcedc8a4d502a9b1fe3f0f2860c62b576b384fab4

5c4a8798162224fba85c25e8c01bb31790ea20f33f47fbe558eb659c197e0a4e

3d7d6789b96f19a8ab2becf3763707a56143050bff197cb3a6c279cbc66dae8a

0b1b2dfea9895c0377f3a12bd2edbd65ec430b0916f95229984b74c77a5d252b

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

Campaign

GHSA-6x6m-m74g-c89p

References

Credits

Amazon Inspector · finder

Detect & block this

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