Which versions of alibabacloud-code-tool are malicious?

The following PyPI versions of alibabacloud-code-tool are flagged malicious: 2.0.0, 2.0.1, 2.0.2, 2.0.3. Treat any of these as compromised.

How do I remediate alibabacloud-code-tool if I installed it?

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

If alibabacloud-code-tool 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 alibabacloud-code-tool part of a known attack campaign?

Yes — alibabacloud-code-tool is associated with the 2026-02-alibabacloude, RLMA-2026-00055 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 alibabacloud-code-tool 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 alibabacloud-code-tool (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging alibabacloud-code-tool across your stack and pipelines.

Malicious package

alibabacloud-code-toolPyPI

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

MAL-2026-915

Immediate action

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

pip uninstall alibabacloud-code-tool

What this malware does

This package impersonates Alibaba Cloud account and contains highly obfuscated code.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-02-alibabacloude

Reasons (based on the campaign):

typosquatting
impersonation
obfuscation

Malicious versions

4 flagged

2.0.02.0.12.0.22.0.3

Indicators of compromise (SHA-256)

5e4d81a71d0710ac3618ec41e8027ee6a96ae9845ca67b33b950c8d99d8d2e8a

3255cd7d14e208ba6336511f7d99803c1b5ba9b06b9e3423c4284bc7352c3642

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

Campaign

2026-02-alibabacloudeRLMA-2026-00055

References

Credits

Kamil Mańkowski (kam193) · reporter
ReversingLabs · finder

Detect & block this

O3 blocks alibabacloud-code-tool-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