Which versions of dreamfusion are malicious?

The following PyPI versions of dreamfusion are flagged malicious: 9.6. Treat any of these as compromised.

How do I remediate dreamfusion if I installed it?

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

If dreamfusion was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is dreamfusion part of a known attack campaign?

Yes — dreamfusion is associated with the RLMA-2024-11030, 2024-11-byted-dast, RLUA-2026-00283 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 dreamfusion across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dreamfusion (version 9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dreamfusion across your stack and pipelines.

Malicious package

dreamfusionPyPI

Malicious code in dreamfusion (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11580

Immediate action

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

pip uninstall dreamfusion

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

Malicious versions

1 flagged

9.6

Indicators of compromise (SHA-256)

a6e35c466821022095e38d70ba5fef0452e652d53dc228173cedaa7021766baf

dbbd21a8f753b96376e7499da0f6ba286f3bdfbe75d3e14eed3407d737dbe63d

daec888ce25f9bd9cea55776c72cf297d277b11e9dc13e4fa634dab5d11656e4

cc3c58ada75ad7b5513ed496a9998aea3338c7ec2c95a82bf6456167bdbb598f

96bfe5b3c654c4cc9e850ea4b9c1ff7c50827c5ecbab82fd3be4ff466df845fc

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dreamfusion (version 9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dreamfusion across your stack and pipelines.
If you installed it — respond
dreamfusion 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 dreamfusion was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dreamfusion before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. dreamfusion on PyPI has been identified as a malicious package (version 9.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-110302024-11-byted-dastRLUA-2026-00283

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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