Which versions of dpy-bot are malicious?

The following PyPI versions of dpy-bot are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate dpy-bot if I installed it?

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

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

Yes — dpy-bot is associated with the RLMA-2024-03875, RLUA-2024-08172 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 dpy-bot across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dpy-bot (version 1.0).

Malicious package

dpy-botPyPI

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

Malicious code in dpy-bot (PyPI)

MAL-2024-5095

Immediate action

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

pip uninstall dpy-bot

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

3ec940cd3e1c69f7235caab8f4ed441362e3bc15b1384d5ba25417be42b4c2b2

8b630b491e988cadb3c5535d7e4f65dbb763667bdaaccaab9d24ce4784100668

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dpy-bot (version 1.0).
If you installed it — respond
Remove dpy-bot 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 dpy-bot 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. dpy-bot on PyPI has been identified as a malicious package (version 1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03875RLUA-2024-08172

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks dpy-bot-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