Which versions of licloud are malicious?

The following PyPI versions of licloud are flagged malicious: 0.2.7a0, 0.2.8. Treat any of these as compromised.

How do I remediate licloud if I installed it?

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

If licloud was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is licloud part of a known attack campaign?

Yes — licloud is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-020114, IN-MAL-2026-020117 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 licloud across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for licloud (2 malicious versions).

Malicious package

licloudPyPI

Advisory published Sep 16, 2026Updated Sep 17, 2026

licloud is a confirmed malicious PyPI package (MAL-2026-16219) that steals credentials and exfiltrates sensitive data (malicious versions 0.2.7a0, 0.2.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in licloud (PyPI)

MAL-2026-16219

Immediate action

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

pip uninstall licloud

What this malware does

setup.py unconditionally collects the installer's OS name, username, and hostname and POSTs them to a hardcoded plain-HTTP bare-IP endpoint (http://182.92.143.23/collect.php) before invoking setup(). The beacon fires on pip install without user consent and is unrelated to the package's stated purpose (an 'LLM gateway SDK'). The destination is a bare IP over cleartext HTTP, not a documented publisher endpoint, and the payload identifies the installer host (os, user, host) with a package tag for follow-on targeting.

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

2 flagged

0.2.7a00.2.8

Indicators of compromise (SHA-256)

5e2bddcfca980297be9856fbbc3eeab78253c51efe034bd92b9e8b52ed9aacc6

380753d9b58e068e84b5bd87242ad31e4b833cdcc056021925aa2dcc91633b46

6d54491d6771e80019937f2da76f1b1a4067e54492d4c0ef4c3a75e8719e2e5c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for licloud (2 malicious versions).
If you installed it — respond
licloud 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 licloud was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. licloud on PyPI has been identified as a malicious package (versions 0.2.7a0, 0.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-020114IN-MAL-2026-020117

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database