Which versions of cloudx-base are malicious?

The following PyPI versions of cloudx-base are flagged malicious: 0.1.12, 1.2.0, 1.2.1. Treat any of these as compromised.

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

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

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

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

Malicious package

cloudx-basePyPI

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

MAL-2025-6480

Immediate action

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

pip uninstall cloudx-base

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

3 flagged

0.1.121.2.01.2.1

Indicators of compromise (SHA-256)

4bb2f7047ec34a36a64dcf7a0963fc13979e8685c6d0c4b492a6c767042f12f7

02398a8a3bbb2694d84660a412047911960c6a743176d20b3127262057b7da49

e6149ee730ff938a43a0991fe084446193db7c0a8c7269623f84679ed6378b3c

2e2d2c15300b9d639ce9e21b382a2658b9ba22fdb6f9c7cffabcf946193826b7

7968a6336370fee9a1051ec046892291f3f60abbd47f548f10630e5eb8617e22

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

Campaign

RLMA-2025-03565GENERIC-standard-pypi-install-pentestRLUA-2026-00198

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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