Which versions of discord-token-lib are malicious?

The following PyPI versions of discord-token-lib are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate discord-token-lib if I installed it?

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

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

Yes — discord-token-lib is associated with the 2024-09-discord-token-lib 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 discord-token-lib 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 discord-token-lib (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging discord-token-lib across your stack and pipelines.

Malicious package

discord-token-libPyPI

Malicious code in discord-token-lib (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12257

Immediate action

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

pip uninstall discord-token-lib

What this malware does

osint packages promise to be OSINT tool, however, when providing the username to search for, the package attempts to exfiltrate Discord tokens from the user.

The original package suggests being a library for Discord exfiltration, what is suspicious on its own, but in addition, the entry point located in main.py exfiltrate local Discord tokens to a hardcoded webhook.

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

Campaign: 2024-09-discord-token-lib

Reasons (based on the campaign):

exfiltration-generic
action-hidden-in-lib-usage

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

a16f42bf80d4ad7d1b19cd1d5edbd1c4147f559f76c5c41a00adf1d605e1868d

44f591d196b048c4cad8da1cc1399681e22a2d5786fb212fda7c920aed8c2b07

40da8c2a663c0510ae1ed1adf805fe279126849610f3327d58815867ffbcfcdf

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

Campaign

2024-09-discord-token-lib

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks discord-token-lib-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