Which versions of ddim are malicious?

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

How do I remediate ddim if I installed it?

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

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

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

Malicious package

ddimPyPI

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

MAL-2024-11570

Immediate action

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

pip uninstall ddim

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)

bed81cf4dcd50b830e6afab08eb20aff7cc0c84ec5c437344bd759e2cd88cd0a

d4b6276cfcf42041983e77d1c386038f5c594e9077842dedc74a5fe665af5fcf

c8ce1850b575ef11a2b475f0451a62134cb8af0fbd39dc812da541dc59987f36

ed1cbb728984e05ccb0575a64862ef33e965cb1e7213786ee56d10e956408d11

1ba1087c704f290567b5ee57f78fe1965da80aa76dfab975a3bd12e19b91994a

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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