Which versions of disocrd are malicious?

The following PyPI versions of disocrd are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate disocrd if I installed it?

Remove disocrd from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed disocrd — how do I know if it already compromised me?

If disocrd was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is disocrd part of a known attack campaign?

Yes — disocrd is associated with the RLMA-2024-03869, RLUA-2024-08166 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 disocrd across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for disocrd (version 1.0.0).

Malicious package

disocrdPyPI

disocrd is a confirmed malicious PyPI package (MAL-2024-5089) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in disocrd (PyPI)

MAL-2024-5089

Immediate action

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

pip uninstall disocrd

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8f70bf521a0d71149f2191d46bf66c4115023018c61fe4ab39e40467f202f675

e103eb612642147f4d735ba5ccacf909a69a55fcc443921d0bd2931b3b51a3e4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for disocrd (version 1.0.0).
If you installed it — respond
Remove disocrd from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If disocrd was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. disocrd on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03869RLUA-2024-08166

References

research.jfrog.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks disocrd-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database