Which versions of icloudprocessor are malicious?

The following PyPI versions of icloudprocessor are flagged malicious: 0.1.0, 1.0.0, 1.0.1, 1.0.7, 1.0.9, 1.0.10. Treat any of these as compromised.

How do I remediate icloudprocessor if I installed it?

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

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

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

Malicious package

icloudprocessorPyPI

Malicious code in icloudprocessor (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-449

Immediate action

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

pip uninstall icloudprocessor

What this malware does

During importing, the package starts a thread that exfiltrates user's files

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

Campaign: 2026-01-icloudprocessor

Reasons (based on the campaign):

files-exfiltration

Malicious versions

6 flagged

0.1.01.0.01.0.11.0.71.0.91.0.10

Indicators of compromise (SHA-256)

67b215e1995682b83e1afa8c297ecbdfe93d12db8cc11341b6bda84116d95814

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

Campaign

2026-01-icloudprocessor

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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