Which versions of discordbotstatus are malicious?

The following PyPI versions of discordbotstatus are flagged malicious: 0.6.7. Treat any of these as compromised.

How do I remediate discordbotstatus if I installed it?

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

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

Yes — discordbotstatus is associated with the RLMA-2025-00459, 2024-12-discordbotstatus, RLUA-2026-00271 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 discordbotstatus 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 discordbotstatus (version 0.6.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging discordbotstatus across your stack and pipelines.

Malicious package

discordbotstatusPyPI

Malicious code in discordbotstatus (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-920

Immediate action

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

pip uninstall discordbotstatus

What this malware does

Package clones another package and hides a code to download and run a malicious exe file (an infostealer with high VT detection)

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

Campaign: 2024-12-discordbotstatus

Reasons (based on the campaign):

clones-real-package
Downloads and executes a remote executable.
infostealer

Malicious versions

1 flagged

0.6.7

Indicators of compromise (SHA-256)

86f8cdb3ebd03eb15ffca651714087164178302fd28712d8f93db9afc1efa534

04f85af7a716eef0e3ba184bfdbb9730199034bb964be77682dd8b3ecac2caa2

2dbd628d2baf4f55c8f9c9dcd441ae7deeee86379f73dd79beb48e41d4bfbe8f

ee161bf0f827abc703e8d03a5229b19f70f9dcc9363901e8f5979bade99ae520

546d6e8e6d893c5dc351f84d497b909f9a71a9a9d1bb55725a86764a477451fb

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

Campaign

RLMA-2025-004592024-12-discordbotstatusRLUA-2026-00271

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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