What does the foundry-jupyter-extension malware do?

Installing or importing the module triggers exfiltration of environmental variables Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-07-foundry-jupyter-extension Reasons (based on the campaign): - exfiltration-env-variables - The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk. - The package overrides the install command in setup.py to execute malicious code during installation. The OpenSSF Package Analysis project identified 'foundry-jupyter-extension' @ 0.23.0 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated wit

Which versions of foundry-jupyter-extension are malicious?

The following PyPI versions of foundry-jupyter-extension are flagged malicious: 0.20.0, 0.21.0, 0.22.0, 0.23.0, 800.23.0. Treat any of these as compromised.

How do I remediate foundry-jupyter-extension if I installed it?

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

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

Yes — foundry-jupyter-extension is associated with the 2025-07-foundry-jupyter-extension 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 foundry-jupyter-extension 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 foundry-jupyter-extension (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging foundry-jupyter-extension across your stack and pipelines.

Malicious package

foundry-jupyter-extensionPyPI

Malicious code in foundry-jupyter-extension (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6248

Immediate action

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

pip uninstall foundry-jupyter-extension

What this malware does

Installing or importing the module triggers exfiltration of environmental variables

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-07-foundry-jupyter-extension

Reasons (based on the campaign):

exfiltration-env-variables
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

The OpenSSF Package Analysis project identified 'foundry-jupyter-extension' @ 0.23.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

5 flagged

0.20.00.21.00.22.00.23.0800.23.0

Indicators of compromise (SHA-256)

18120bcaae1e9da4251368d123f8dfe860d3c2af2fbbb8393d2a323c5c8571f2

33ddd7b7b48ab562ae5eabf7493831b302bbf4d725307e51e7563947ddfeefbb

8114162af3676e6c75f96e1dc953dae363e41fab4e9b3ce75a84b261aece0113

b151318ecdd7d06f606841bd6b827b3f6a5b968907db8b96e74cd739e51368a7

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 foundry-jupyter-extension (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging foundry-jupyter-extension across your stack and pipelines.
If you installed it — respond
foundry-jupyter-extension 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 foundry-jupyter-extension 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 foundry-jupyter-extension 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. foundry-jupyter-extension on PyPI has been identified as a malicious package (versions 0.20.0, 0.21.0, 0.22.0, 0.23.0, 800.23.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-07-foundry-jupyter-extension

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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