Which versions of py-slugify are malicious?

The following PyPI versions of py-slugify are flagged malicious: 0.8.2. Treat any of these as compromised.

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

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

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

Yes — py-slugify is associated with the 2026-07-yt-api-dlp 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 py-slugify 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 py-slugify (version 0.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging py-slugify across your stack and pipelines.

Malicious package

py-slugifyPyPI

Malicious code in py-slugify (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-6976

Immediate action

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

pip uninstall py-slugify

What this malware does

During import, this malicious copy of a legitimate package downloads an encrypted data disguise as an image. It contains an archive with a next-stage script that uses the Polygon blockchain (contract 0xC7c9026a3a7e27ec6Ce2D09B19FC1FB4bc978BBb) to get the C2 address. The script then communicates with C2 over an encrypted channel to get further commands and ensures persistence. C2 delivers an executable that is executed by loading it into the memory of another process. During analysis, the encryption key and delivered binary contained test data suggesting the author experiments with building a botnet.

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

Campaign: 2026-07-yt-api-dlp

Reasons (based on the campaign):

peristence-autorun
Downloads and executes a remote malicious script.
clones-real-package
persistence
custom-crypto
data-from-blockchain

Malicious versions

1 flagged

0.8.2

Indicators of compromise (SHA-256)

67a9d1e498fcf994bbfd8e10bde000990fe4579a88ba5b20848beabac1ae44cc

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

Campaign

2026-07-yt-api-dlp

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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