Which versions of @ensdomains/ccip-read-worker-viem are malicious?

The following npm versions of @ensdomains/ccip-read-worker-viem are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate @ensdomains/ccip-read-worker-viem if I installed it?

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

If @ensdomains/ccip-read-worker-viem 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/ccip-read-worker-viem part of a known attack campaign?

Yes — @ensdomains/ccip-read-worker-viem is associated with the GHSA-g8cp-w9cm-p948 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/ccip-read-worker-viem 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/ccip-read-worker-viem (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/ccip-read-worker-viem across your stack and pipelines.

Malicious package

@ensdomains/ccip-read-worker-viemnpm

Malicious code in @ensdomains/ccip-read-worker-viem (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190725

Immediate action

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

npm uninstall @ensdomains/ccip-read-worker-viem

What this malware does

The package @ensdomains/ccip-read-worker-viem 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)

7f1bb2155c329c533747095a843514e71c518ee8ad24adc976516564dd4605a9

57b104a492d5893772494de67a98f0114e695a8d24e0444d12d0963029fc4b32

b162fbb0647ca930b4ec8594d4317ce91970c3b905ae4a904f4b4034a92db181

9ca84514150232e25a61bdecf7a00797cd9c2e80056b35159603da3322b321ba

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/ccip-read-worker-viem (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/ccip-read-worker-viem across your stack and pipelines.
If you installed it — respond
@ensdomains/ccip-read-worker-viem 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/ccip-read-worker-viem 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/ccip-read-worker-viem 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/ccip-read-worker-viem 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-g8cp-w9cm-p948

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ensdomains/ccip-read-worker-viem-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