Which versions of sumo-py-cli are malicious?

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

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

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

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

Yes — sumo-py-cli is associated with the RLMA-2024-11174, GENERIC-standard-pypi-install-pentest, RLUA-2026-00786 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 sumo-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 sumo-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 sumo-py-cli across your stack and pipelines.

Malicious package

sumo-py-cliPyPI

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

MAL-2024-11715

Immediate action

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

pip uninstall sumo-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)

504f2580d546e21d70334d83a4d81f3d59294d38bd9b3f82db2c8284e0a89216

8a999ec53654855b98c94663cccb9513781a7ffed0ef915a695a0c3a920fcaf8

6ed9233fda861428b541d5a3188300bb67c877f6998c43e808dc5910b7113b4d

ff31f4b93d445723f8df3e175790fd1a8350d9c91851b44ebc5cb8986d163d12

7d883fc276c89db59b9657c93354bba725df7d6eac608c88827fffc5c6a139fb

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 sumo-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 sumo-py-cli across your stack and pipelines.
If you installed it — respond
sumo-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 sumo-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 sumo-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. sumo-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-11174GENERIC-standard-pypi-install-pentestRLUA-2026-00786

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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