Which versions of @ensdomains/thorin are malicious?

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

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

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

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

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

Malicious package

@ensdomains/thorinnpm

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

MAL-2025-190739

Immediate action

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

npm uninstall @ensdomains/thorin

What this malware does

The package @ensdomains/thorin 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.6.51

Indicators of compromise (SHA-256)

090a3871267b78737fee413228eecf297541c68534e534ae1d8283b2f5bbc17c

5b9c01ec760c3b86219974f606ccd10c9b872a38f725916392971a20b50e4b57

f8ca81417fb4649bedca04f22f30c29b8c8b76c6354c1e021a382280955198da

96aa2b6056b8e3d34a91b3611541b5e1d3317e6255168c99bcea442899fe3995

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

Campaign

GHSA-qpqq-p6gg-rqp2

References

Credits

Amazon Inspector · finder

Detect & block this

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