Which versions of pyext6cc8cd are malicious?

The following PyPI versions of pyext6cc8cd are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate pyext6cc8cd if I installed it?

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

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

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

Malicious package

pyext6cc8cdPyPI

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

MAL-2026-6488

Immediate action

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

pip uninstall pyext6cc8cd

What this malware does

On pip install, setup.py decodes a hex string via bytes.fromhex("6f70656e202d612043616c63756c61746f72").decode().split() to the argv open -a Calculator and executes it through subprocess.Popen before setuptools.setup() is called. The command runs unconditionally as part of the install lifecycle. The package metadata is placeholder (Author, Home-page, and Description are all 'UNKNOWN') and the package ships no functional code, so this is a proof-of-concept / test artifact demonstrating arbitrary install-time command execution. While the decoded payload here only opens macOS Calculator, the hex obfuscation of the argv is a deliberate technique to evade scanners that grep setup.py for literal command strings, and the same primitive trivially swaps to a destructive or exfiltration payload. Installers should treat this version as untrusted install-time code execution.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f98319eaa02d50e8a098d9cfaaca054df5acc8238dd08b2e24899f700e029a07

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

Campaign

IN-MAL-2026-007566

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

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