Which versions of dider are malicious?

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

How do I remediate dider if I installed it?

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

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

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

Search your lockfiles and build artifacts for dider (version 1.0).

Malicious package

diderPyPI

dider is a confirmed malicious PyPI package (MAL-2024-5050) 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 dider (PyPI)

MAL-2024-5050

Immediate action

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

pip uninstall dider

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

4a7abb5bf521cf423a11ea1b166582cd1227447017cc448bcdffffc526d62139

c1491b96849e8b755aca95bf668165c9b1c088e4f49ea0d15e4547b3628629eb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dider (version 1.0).
If you installed it — respond
Remove dider 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 dider 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. dider 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-03830RLUA-2024-08126

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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