Which versions of foundy-toolkit are malicious?

The following npm versions of foundy-toolkit are flagged malicious: 1.5.79. Treat any of these as compromised.

How do I remediate foundy-toolkit if I installed it?

foundy-toolkit is a typosquat — you almost certainly intended a legitimately-named package. Remove foundy-toolkit, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed foundy-toolkit — how do I know if it already compromised me?

If foundy-toolkit 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 foundy-toolkit part of a known attack campaign?

Yes — foundy-toolkit is associated with the GHSA-48f2-rw49-vgx3, IN-MAL-2026-003375, IN-MAL-2026-003376 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 foundy-toolkit 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 foundy-toolkit (version 1.5.79). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging foundy-toolkit across your stack and pipelines.

Malicious package

foundy-toolkitnpm

Malicious code in foundy-toolkit (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4242

Immediate action

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

npm uninstall foundy-toolkit

What this malware does

On npm install, the package's postinstall script runs an inline node -e that shells out to curl -fsSL against an ephemeral Pinggy free-tier tunnel host (rqnyz-2605-7280-7--2000-c51.run.pinggy-free.link/npm/-/binary/telemetry), writes the response to the hidden path /tmp/.node-cache, chmods it executable, and launches it in the background with errors swallowed by try/catch. The download URL is not version-pinned, no hash or signature is verified, the destination host is an anonymous attacker-controlled tunnel (not a publisher CDN, not GitHub releases), and the binary's purpose is undocumented behind a telemetry cover path. The package name foundy-toolkit is a one-character deletion of foundry-toolkit, and index.js invokes forge --version to mimic the Foundry (foundry-rs) toolchain, while metadata ([email protected], github.com/foundry/foundy-toolkit) appears fabricated. Any developer or CI system that runs npm install foundy-toolkit executes attacker-controlled bytes from a mutable anonymous host.

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.

Malicious versions

1 flagged

1.5.79

Indicators of compromise (SHA-256)

fa92eec022bddec393b3c4c2ad4d2b206650cad3900c98e5a4f667a5f66e29c4

d117fe522ec0aee9271963b02fb9a61b7e5005b5494331368b58f46c05c944cd

f0ae9a0d2137837bfa885cedc2faefcd388987eb9d4e0a460c9cabd242a69a41

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for foundy-toolkit (version 1.5.79). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging foundy-toolkit across your stack and pipelines.
If you installed it — respond
foundy-toolkit is a typosquat — you almost certainly intended a legitimately-named package. Remove foundy-toolkit, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If foundy-toolkit 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 foundy-toolkit 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. foundy-toolkit on npm has been identified as a malicious package (version 1.5.79 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-48f2-rw49-vgx3IN-MAL-2026-003375IN-MAL-2026-003376

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks foundy-toolkit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring