Which versions of create-hardhat3-app are malicious?

The following npm versions of create-hardhat3-app are flagged malicious: 1.1.1, 1.1.2, 1.1.3, 1.1.4. Treat any of these as compromised.

How do I remediate create-hardhat3-app if I installed it?

create-hardhat3-app 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 create-hardhat3-app — how do I know if it already compromised me?

If create-hardhat3-app 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 create-hardhat3-app part of a known attack campaign?

Yes — create-hardhat3-app is associated with the GHSA-9q97-4cxq-xw96 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 create-hardhat3-app 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 create-hardhat3-app (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging create-hardhat3-app across your stack and pipelines.

Malicious package

create-hardhat3-appnpm

Malicious code in create-hardhat3-app (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190839

Immediate action

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

npm uninstall create-hardhat3-app

What this malware does

The package create-hardhat3-app 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

4 flagged

1.1.11.1.21.1.31.1.4

Indicators of compromise (SHA-256)

c954b0cabe929a310d28d077f4c3c62af90a694bf1a1a7cec092a2247f225b1b

a5a1dad1ef411b38a2b87787581837e9c9f5a26fff790d14057d04ca67c06ddc

d9428e2899f9a69c201dcec3ae0f0c9664dd4ebaf5725c1eb6dde088e8896e02

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

Campaign

GHSA-9q97-4cxq-xw96

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks create-hardhat3-app-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