Which versions of imagedreamfusion are malicious?

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

How do I remediate imagedreamfusion if I installed it?

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

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

Yes — imagedreamfusion is associated with the RLMA-2024-11067, 2024-11-byted-dast, RLUA-2026-00422 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 imagedreamfusion 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 imagedreamfusion (version 9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging imagedreamfusion across your stack and pipelines.

Malicious package

imagedreamfusionPyPI

imagedreamfusion is a confirmed malicious PyPI package (MAL-2024-11614) that steals credentials and exfiltrates sensitive data (malicious version 9.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in imagedreamfusion (PyPI)

MAL-2024-11614

Immediate action

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

pip uninstall imagedreamfusion

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)

26af36048f2ec0096f0947599221bfa93d1271ede0d619a7227a99a508b63b5c

ce03efbb5c69cff5be021e69a1c326509f73ba37e9e06e7855a81b10b0e6dffd

a6d6718a5b7231657a334b5a35b2053de510f4c15bdf137085121d29b5086121

4db4bdd9605cf2290f5bec9a95d5955ad810900373d60a260db5fb97f24936d5

9afe48fd8eae9610f9190c8967ba1598c69af048b55942d619bff2e0da450b30

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 imagedreamfusion (version 9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging imagedreamfusion across your stack and pipelines.
If you installed it — respond
imagedreamfusion 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 imagedreamfusion 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 imagedreamfusion 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. imagedreamfusion 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-110672024-11-byted-dastRLUA-2026-00422

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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