What does the foundry-toolkit malware do?

The package foundry-toolkit was found to contain malicious code. The OpenSSF Package Analysis project identified 'foundry-toolkit' @ 1.0.11 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of foundry-toolkit are malicious?

The following npm versions of foundry-toolkit are flagged malicious: 1.0.1, 1.0.2, 1.0.5, 1.0.9, 1.0.11, 1.0.14. Treat any of these as compromised.

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

Remove foundry-toolkit from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If foundry-toolkit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find foundry-toolkit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for foundry-toolkit (6 malicious versions).

Malicious package

foundry-toolkitnpm

Advisory published Feb 26, 2026Updated Mar 2, 2026

foundry-toolkit is a confirmed malicious npm package (MAL-2026-1052) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 1.0.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in foundry-toolkit (npm)

MAL-2026-1052

Immediate action

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

npm uninstall foundry-toolkit

What this malware does

The package foundry-toolkit was found to contain malicious code.

The OpenSSF Package Analysis project identified 'foundry-toolkit' @ 1.0.11 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

6 flagged

1.0.11.0.21.0.51.0.91.0.111.0.14

Indicators of compromise (SHA-256)

3cf89e35ab285581fe9085242663e96ab85dc5372633551f98c0bf406715a6b2

9c0e248201666dadac5d03f4b6377a8df3fe5e0cb00ad0223d9da80dc8c07543

cf5423d6ae5d78958a3a5767a6d19591200596a5634427b8f7769705de2ccc5f

3762da1ba2c85b0e0210a98196cefcf7914ab00712944886cb47409656409ac6

44b93dc5ab17da98c60cb972bea12ad4520e07c984b696d03899e70893c450c8

44eb04016af9a8d0b91bc628f6a6d69b0fa4c0e9f2f54b4faa7cc81e19485a58

cb16385d7092af7cebb2b2a64518b638584e8837d4b215d9c3fa23d2a84fe9c0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for foundry-toolkit (6 malicious versions).
If you installed it — respond
Remove foundry-toolkit from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If foundry-toolkit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. foundry-toolkit on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.5, 1.0.9, 1.0.11, 1.0.14 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database