Which versions of cmdb-worker-pckg are malicious?

The following PyPI versions of cmdb-worker-pckg are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate cmdb-worker-pckg if I installed it?

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

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

Yes — cmdb-worker-pckg is associated with the RLMA-2024-11005, GENERIC-standard-pypi-install-pentest, RLUA-2026-00199 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 cmdb-worker-pckg 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 cmdb-worker-pckg (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cmdb-worker-pckg across your stack and pipelines.

Malicious package

cmdb-worker-pckgPyPI

Malicious code in cmdb-worker-pckg (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11558

Immediate action

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

pip uninstall cmdb-worker-pckg

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d6596e2e483346b2c37f6bad8bdff61246aebb707abdda9be956be3334eb4a0a

606eb49d8f0889717b3c8ce4fa352a5f34ac8680278c91f597609e9f36252030

f0039cc4672b957b253c70bf7a3d084574f8a10d21d6bc42d0fac2f2a3fd8400

41c882a10710614664c27f31919cfc5810e068a612c5ee3517bdf65e56e3d521

e5ca02c4e17773efd7032fd4ff360c7c82daa0c4d4f43547ab9560cf2e066846

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 cmdb-worker-pckg (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cmdb-worker-pckg across your stack and pipelines.
If you installed it — respond
cmdb-worker-pckg 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 cmdb-worker-pckg 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 cmdb-worker-pckg 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. cmdb-worker-pckg on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-11005GENERIC-standard-pypi-install-pentestRLUA-2026-00199

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks cmdb-worker-pckg-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