Which versions of bigpyx are malicious?

The following PyPI versions of bigpyx are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate bigpyx if I installed it?

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

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

Yes — bigpyx is associated with the 2025-12-graphnode 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 bigpyx across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bigpyx (2 malicious versions).

Malicious package

bigpyxPyPI

Advisory published Dec 10, 2025Updated Feb 11, 2026

bigpyx is a confirmed malicious PyPI package (MAL-2025-192430) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigpyx (PyPI)

MAL-2025-192430

Immediate action

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

pip uninstall bigpyx

What this malware does

Continuation of the campaign with a slight different obfuscation of the malicious code, but there seems to be no difference in the behavior. The malicious code is downloaded and executed

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

Campaign: 2025-12-graphnode

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote malicious script.
clones-real-package

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

7a1bcd636394f1505534cf691576b00e8686aa14474e8a209c94f8213310b128

4377653ca69c53a9f9d8e1782f987a0f7133480252684de14c70a7ecd92715ea

d6d4cd1538dbf7f829824bb8f226a4f1b0550abd89dee5dc8235d2fae361a055

Detection & response playbook

Credential / info stealer

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

Campaign

2025-12-graphnode

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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