Which versions of iron-shield-miniapp are malicious?

The following npm versions of iron-shield-miniapp are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate iron-shield-miniapp if I installed it?

iron-shield-miniapp 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 iron-shield-miniapp — how do I know if it already compromised me?

If iron-shield-miniapp 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 iron-shield-miniapp part of a known attack campaign?

Yes — iron-shield-miniapp is associated with the GHSA-ghrh-qj3w-c6jg 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 iron-shield-miniapp 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 iron-shield-miniapp (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging iron-shield-miniapp across your stack and pipelines.

Malicious package

iron-shield-miniappnpm

Malicious code in iron-shield-miniapp (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190773

Immediate action

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

npm uninstall iron-shield-miniapp

What this malware does

The package iron-shield-miniapp 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.2

Indicators of compromise (SHA-256)

3cbabce333453b61afebaab4e028eb679742172f9b0974bcebb1ca5513e21348

6a7b0e4007bb817da7fd19c6ddd7f073f585337504d8ac60541b07e162398b70

0f51888d5cb4ece89ddada73d30d0d085c068a9284af7297d52ceb394efd9c88

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

Campaign

GHSA-ghrh-qj3w-c6jg

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks iron-shield-miniapp-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