Which versions of gnosis-py are malicious?

The following PyPI versions of gnosis-py are flagged malicious: 0.0.0, 2.4.7. Treat any of these as compromised.

How do I remediate gnosis-py if I installed it?

gnosis-py 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 gnosis-py — how do I know if it already compromised me?

If gnosis-py 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.

Is gnosis-py part of a known attack campaign?

Yes — gnosis-py is associated with the GENERIC-standard-pypi-install-pentest 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 gnosis-py across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gnosis-py (2 malicious versions).

Malicious package

gnosis-pyPyPI

Advisory published Oct 6, 2025Updated Dec 31, 2025

gnosis-py is a confirmed malicious PyPI package (MAL-2025-191740) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.0, 2.4.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gnosis-py (PyPI)

MAL-2025-191740

Immediate action

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

pip uninstall gnosis-py

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

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.

Malicious versions

2 flagged

0.0.02.4.7

Indicators of compromise (SHA-256)

b25d4492e774b757fd9157b4197035c47081be2e6921d1814e8dfcb37ea71455

42112b8b2e7c96d9c3a5a188bebf3539cba140ccfdcc721ea9952259b8893721

36a27d3a38c90d566c58b46a90efa9c5e88e78d10c5bb7b41da758b2243f370b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for gnosis-py (2 malicious versions).
If you installed it — respond
gnosis-py 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 gnosis-py 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. gnosis-py on PyPI has been identified as a malicious package (versions 0.0.0, 2.4.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks gnosis-py-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

Explore

All malware advisories How O3 detects malware Vulnerability database