Which versions of alpha-booster are malicious?

The following PyPI versions of alpha-booster are flagged malicious: 1.0, 1.1, 1.2, 1.3. Treat any of these as compromised.

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

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

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

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

Malicious package

alpha-boosterPyPI

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

MAL-2025-6431

Immediate action

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

pip uninstall alpha-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

4 flagged

1.01.11.21.3

Indicators of compromise (SHA-256)

98b1011117e418ec81af4a63288e744354e3eff71e3e587a1d07905c0a2871c2

4e82c59169c5e251a83750ab4b484b1fe04e0d576e49f30ceea9ccafc268d5fb

8fe7614b282cfa81278bc61bde1998e286fe7554c1d37b4c3185718c6e54f6af

693579d2cfeb801fd45dcb29a7ecc42dc73ab03cef3e9987c4fa4832706c6c22

d4cd20f74541f773862aab8c5b6df87d5bf90eb6bb82cd215ddff6c9d869f416

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

Campaign

RLMA-2025-035152025-05-discord-boosterRLUA-2026-00060

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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