Which versions of st-py-de-cli are malicious?

The following PyPI versions of st-py-de-cli are flagged malicious: 1.9.9. Treat any of these as compromised.

How do I remediate st-py-de-cli if I installed it?

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

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

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

Malicious package

st-py-de-cliPyPI

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

MAL-2025-41768

Immediate action

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

pip uninstall st-py-de-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

1.9.9

Indicators of compromise (SHA-256)

740cd15c46249ef8392ee0768d88189dc3589522b3e7206893d2c56e341652cf

b57204d0121ef56e533345f51682f0baa2f8d976925e7653845009d3454870d0

a0110859887f6cd8d6e81ff1c6715dd4a5d2a1c84c28b71cb09320e33e10cce5

bbb954f7620f2b5375ffd61f8e9af9023afd5e07519da2eb16c20c2ffc56eb7d

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

Campaign

RLMA-2025-04266GENERIC-standard-pypi-install-pentestRLUA-2026-00779

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks st-py-de-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