Which versions of graddio are malicious?

The following PyPI versions of graddio are flagged malicious: 0.226.51. Treat any of these as compromised.

How do I remediate graddio if I installed it?

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

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

Yes — graddio is associated with the 2025-06-alembic-util 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 graddio 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 graddio (version 0.226.51). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graddio across your stack and pipelines.

Malicious package

graddioPyPI

Malicious code in graddio (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3704

Immediate action

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

pip uninstall graddio

What this malware does

During installation, package exfiltrates some basic info to a GitHub issue comment, and then attempt to set up a persistent infostealer focused on exfiltrating crypto wallets and browsers data. Likely continuation of 2026-05-py-requests

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

Campaign: 2025-06-alembic-util

Reasons (based on the campaign):

infostealer
The package overrides the install command in setup.py to execute malicious code during installation.
crypto-related
Downloads and executes a remote malicious script.
exfiltration-browser-data
exfiltration-crypto
persistence
typosquatting

Malicious versions

1 flagged

0.226.51

Indicators of compromise (SHA-256)

cf6bbc8eaafef42ed4e5740b1ff94df7749de4241d44846467b438db586399ba

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

Campaign

2025-06-alembic-util

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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