Which versions of discord-booster are malicious?

The following PyPI versions of discord-booster are flagged malicious: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9. Treat any of these as compromised.

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

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

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

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

Malicious package

discord-boosterPyPI

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

MAL-2025-6495

Immediate action

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

pip uninstall discord-booster

What this malware does

Code downloads and runs the remote executable. While the current link seems not to work, the previous versions had an embedded infostealer instead.

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

Campaign: 2025-05-discord-booster

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

9 flagged

0.10.20.30.40.50.60.70.80.9

Indicators of compromise (SHA-256)

d54ad60e52de2d2211e91a11fe31093738cf5b0a667aeb14e85d401620ec4469

a6170b165dae85bb1a871b758746f2d8ba437d22a209451a9d655cdf3dc93830

f561c13e7822efe2d480bce32956c66b8eaabe69e40665997628b7b927e4e763

97b4f06c13d19371735157a94f911094c126d9525e4cdb6d7b53f4aa19e2887c

78bc9119c8fecd435e35c9cd07b3b344baacd6e60cd661250dde3e957db61a16

732e17bb7c6ad11c7774831048158a9d79beccea0ffe9eed6c76d12954af21b2

e1cc6019d91de385658a13b7f1da0dfa28d27bd75924519e8d230271c10dbde5

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

Campaign

RLMA-2025-035862025-05-discord-boosterRLUA-2026-00267RLUA-2026-02069

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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