Which versions of cloudx-auth are malicious?

The following PyPI versions of cloudx-auth are flagged malicious: 1.3.1. Treat any of these as compromised.

How do I remediate cloudx-auth if I installed it?

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

If cloudx-auth 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 cloudx-auth part of a known attack campaign?

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

Malicious package

cloudx-authPyPI

Malicious code in cloudx-auth (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6479

Immediate action

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

pip uninstall cloudx-auth

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.3.1

Indicators of compromise (SHA-256)

a563601a7a339b185e43b0f1ba32c66f30717e58f3a328049ac5135394250637

c01abe9b7878bef2fce5cc080066338599ac77b72da78413c0396548b13ac10e

069fce9e881c6c5a7b7e17d06814e25e193f0ac67903e80242a1a22de7c7d69d

39a7a45aa4f13d59ec5dbea3c2678c00046ec982aff0ed2304421dc23b680bfd

3c9d427ec58e40627200d4a5893d6f724c8045dfa2a3b77ff59eae19e510a45f

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

Campaign

RLMA-2025-03564GENERIC-standard-pypi-install-pentestRLUA-2026-00197

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks cloudx-auth-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