Which versions of test-foundry-app are malicious?

The following npm versions of test-foundry-app are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate test-foundry-app if I installed it?

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

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

Yes — test-foundry-app is associated with the GHSA-pgpr-q3gr-j9hq 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 test-foundry-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 test-foundry-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 test-foundry-app across your stack and pipelines.

Malicious package

test-foundry-appnpm

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

MAL-2025-190860

Immediate action

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

npm uninstall test-foundry-app

What this malware does

The package test-foundry-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.0.11.0.21.0.31.0.4

Indicators of compromise (SHA-256)

9b0d08ebcb8c6a236f7c4c5785ac4f1ec1b4e2ede40366d6fc439473f946b332

9961bd7169c780d2201b29f4ada6a92f1c9d6eb26c8443c0365a7ea218daa7c8

e225a5a2e64d1b8979f39631d495ec4d7e7524ceb683bb2e10c69c86db6f8650

cce1d3fb7597c6b0c3742a9cd217fb21a0a1546c694c88c5899c4606d51663fc

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 test-foundry-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 test-foundry-app across your stack and pipelines.
If you installed it — respond
test-foundry-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 test-foundry-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 test-foundry-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. test-foundry-app on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pgpr-q3gr-j9hq

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test-foundry-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