Which versions of daft-dashboard are malicious?

The following PyPI versions of daft-dashboard are flagged malicious: 0.0.0.1. Treat any of these as compromised.

How do I remediate daft-dashboard if I installed it?

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

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

Yes — daft-dashboard is associated with the RLMA-2025-01951 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 daft-dashboard across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for daft-dashboard (version 0.0.0.1).

Malicious package

daft-dashboardPyPI

daft-dashboard is a confirmed malicious PyPI package (MAL-2025-2953) that executes malicious code on install (malicious version 0.0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in daft-dashboard (PyPI)

MAL-2025-2953

Immediate action

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

pip uninstall daft-dashboard

Malicious versions

1 flagged

0.0.0.1

Indicators of compromise (SHA-256)

e159e4495f59597cdede75d3fe3cd93995a70cf1aacc11b549f6907231d09334

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-01951

Credits

ReversingLabs · finder

Detect & block this

O3 blocks daft-dashboard-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