Which versions of milleday are malicious?

The following PyPI versions of milleday are flagged malicious: 1. Treat any of these as compromised.

How do I remediate milleday if I installed it?

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

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

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

Search your lockfiles and build artifacts for milleday (version 1).

Malicious package

milledayPyPI

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

Malicious code in milleday (PyPI)

MAL-2024-5366

Immediate action

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

pip uninstall milleday

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

2e46b1dd9917be1fc63ebd5f459ba0cfd2fc836691aeaa3ed4a8ccb31020db09

fb3e3cc143602f7adfdc5fbe0766398bcd23348af40a088687f37beac68d26fa

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04148RLUA-2024-08517

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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