Which versions of dashloom are malicious?

The following PyPI versions of dashloom are flagged malicious: 1.0.0, 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate dashloom if I installed it?

dashloom is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — dashloom is associated with the 2026-11-dashloom 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 dashloom across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dashloom (3 malicious versions).

Malicious package

dashloomPyPI

Advisory published Nov 12, 2026Updated Nov 12, 2026

dashloom is a confirmed malicious PyPI package (MAL-2026-19202) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dashloom (PyPI)

MAL-2026-19202

Immediate action

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

pip uninstall dashloom

What this malware does

This package is prepared to be used as a malicious loader. It pins pydash dependency in a vulnerable version allowing reaching out of the object scope when calling pydash.invoke(...). The code to reach it is intended to be delivered from the now-benign GitHub file, which is then splited and passed to the vulnerable function. The same Github user account is also involved in publishing a repository that executes embedded encrypted code when called with specific arguments. The package was originally flagged by PyPI Security.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-11-dashloom

Reasons (based on the campaign):

action-hidden-in-lib-usage
Downloads and executes a remote malicious script.

Malicious versions

3 flagged

1.0.01.1.01.1.1

Indicators of compromise (SHA-256)

ba0285d49d46cd93cdcad1582bb1c013beb3791dc901a0a3c96f3801dba9d909

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for dashloom (3 malicious versions).
If you installed it — respond
dashloom is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dashloom 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. dashloom on PyPI has been identified as a malicious package (versions 1.0.0, 1.1.0, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-11-dashloom

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks dashloom-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database