Which versions of pd-py-cli are malicious?

The following PyPI versions of pd-py-cli are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate pd-py-cli if I installed it?

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

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

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

Malicious package

pd-py-cliPyPI

Malicious code in pd-py-cli (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11656

Immediate action

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

pip uninstall pd-py-cli

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

99.99.99

Indicators of compromise (SHA-256)

dfeb54f5de7628b2eacc4dbaae672a17766f1905a8f08c2e45e3d06c0e49c0e6

d250c642de7333f73e9e14727216eff81720df54b441ef7a6cb1e64a450fe485

a736772e9e597e421d82f4148fe6b608acb28b363db608096df90e782cce4af7

c0a924ce7c4fd513bedd5c9b52d308197b7a86f685f729d8e873b94a8b164a78

14877d15b2f5aa68472fcfaed2b5cdf4bdd11aa5a6358024402ecbfda1c15e57

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

Campaign

RLMA-2024-11112GENERIC-standard-pypi-install-pentestRLUA-2026-00584

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks pd-py-cli-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