Which versions of discord-selfsbotsx are malicious?

The following PyPI versions of discord-selfsbotsx are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate discord-selfsbotsx if I installed it?

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

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

Yes — discord-selfsbotsx is associated with the 2025-11-discord-selfsbotsx, RLMA-2025-06561, RLUA-2026-00269 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-selfsbotsx 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-selfsbotsx (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging discord-selfsbotsx across your stack and pipelines.

Malicious package

discord-selfsbotsxPyPI

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

MAL-2025-191718

Immediate action

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

pip uninstall discord-selfsbotsx

What this malware does

Once run, package downloads and installs an infostealer

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

Campaign: 2025-11-discord-selfsbotsx

Reasons (based on the campaign):

Downloads and executes a remote executable.
infostealer
malware
peristence-autorun

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

1d693217182599c6434c6d03f4a857a0338b46dda49afa188000a948de42ea80

b56aa48c0654abd06a9d624b8c1b5ab4ce170399068d97b994bb4d63635bf18a

d762b62bc1e32d89da07e33977938ccf7b5868f56b22ed931b29045ae12f875e

c4c3324e23fe0fdc0ea0915c2e7c7309e7b97b02395451aceb6d5cc2a7f75241

325d188ac9a6ea235c2dd774e66e34f11ef3aa00687c289765a98e56f0d81ca8

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

Campaign

2025-11-discord-selfsbotsxRLMA-2025-06561RLUA-2026-00269

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks discord-selfsbotsx-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