Which versions of discself are malicious?

The following PyPI versions of discself are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate discself if I installed it?

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

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

Yes — discself is associated with the 2024-09-old-discself 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 discself across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for discself (version 1.0.0).

Malicious package

discselfPyPI

Advisory published Sep 16, 2024Updated Dec 12, 2025

discself is a confirmed malicious PyPI package (MAL-2024-12258) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in discself (PyPI)

MAL-2024-12258

Immediate action

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

pip uninstall discself

What this malware does

Package suggests a code to build bots; however, the code just exfiltrates the token given by the user to the hardcoded Discord webhook. Looking at other activity on the account, it's either research or forgotten WIP/test.

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: 2024-09-old-discself

Reasons (based on the campaign):

action-hidden-in-lib-usage

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

da6f874baf1f1b19d25ce956179469d4c78f72c1e64b1cfa336db9e543c7be8c

271e2fef9fd10cd1a179df1be1e1f92c837d1ecf3d074451a9b1b6205babe511

b632964703138c2175e285be4e1f91611d3bb6c86b8eba814c94265021b56486

Detection & response playbook

Credential / info stealer

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

Campaign

2024-09-old-discself

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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