Which versions of zapier-async-storage are malicious?

The following npm versions of zapier-async-storage are flagged malicious: 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate zapier-async-storage if I installed it?

zapier-async-storage 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 zapier-async-storage — how do I know if it already compromised me?

If zapier-async-storage 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 zapier-async-storage part of a known attack campaign?

Yes — zapier-async-storage is associated with the GHSA-8w6h-9qgr-pfxv 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 zapier-async-storage 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 zapier-async-storage (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zapier-async-storage across your stack and pipelines.

Malicious package

zapier-async-storagenpm

Malicious code in zapier-async-storage (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190788

Immediate action

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

npm uninstall zapier-async-storage

What this malware does

The package zapier-async-storage 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

3 flagged

1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

736c768bb3648b65ecea3f80ac021b56c1ed3c9bd1f1b4eca5c85f790c438a4d

03106802713a8738ac15728a0fdb19774a74ac3ae3aa76b501b8d4b08e8a7e5e

756a8d221ef753d67c13dc4e36e8b0ad6653f31b8b8f336fdb7cb2d238202c57

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

Campaign

GHSA-8w6h-9qgr-pfxv

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zapier-async-storage-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