Which versions of cloushaar-poc-exfil-91827 are malicious?

The following PyPI versions of cloushaar-poc-exfil-91827 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate cloushaar-poc-exfil-91827 if I installed it?

cloushaar-poc-exfil-91827 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 cloushaar-poc-exfil-91827 — how do I know if it already compromised me?

If cloushaar-poc-exfil-91827 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 cloushaar-poc-exfil-91827 part of a known attack campaign?

Yes — cloushaar-poc-exfil-91827 is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-020283 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 cloushaar-poc-exfil-91827 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 cloushaar-poc-exfil-91827 (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cloushaar-poc-exfil-91827 across your stack and pipelines.

Malicious package

cloushaar-poc-exfil-91827PyPI

cloushaar-poc-exfil-91827 is a confirmed malicious PyPI package (MAL-2026-16377) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cloushaar-poc-exfil-91827 (PyPI)

MAL-2026-16377

Immediate action

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

pip uninstall cloushaar-poc-exfil-91827

What this malware does

The package's setup.py, executed automatically during pip install, iterates a hardcoded list of installer-side filesystem paths (/flag, /flag.txt, /app/flag, /root/flag, and similar candidates), reads their contents, and transmits them via urllib.request.urlopen as a query-string parameter to the hardcoded endpoint https://webhook.site/f41d2013-dd84-4139-85f8-8e989e0761b8. The webhook.site host is an anonymous request-collector controlled by whoever provisioned that endpoint. The name and version suggest a proof-of-concept exfiltration package, but the shipped code performs real install-time filesystem reads and outbound HTTP exfiltration against any host that runs pip install on this artifact.

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

0.0.1

Indicators of compromise (SHA-256)

8ec6abf4fcd51274f6bf53cece87bc47051b0751b117e137c68d964b05753e16

58b36f7c6e3e2e536f43b51acc410985240e6de6d7bb1e1d78126131e888806f

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

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-020283

References

Credits

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

Detect & block this

O3 blocks cloushaar-poc-exfil-91827-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