Which versions of cryptgraphy are malicious?

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

How do I remediate cryptgraphy if I installed it?

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

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

Yes — cryptgraphy is associated with the 2026-08-mlflow-otel-instrumentor, IN-MAL-2026-018593 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 cryptgraphy 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 cryptgraphy (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 cryptgraphy across your stack and pipelines.

Malicious package

cryptgraphyPyPI

cryptgraphy is a confirmed malicious PyPI package (MAL-2026-14388) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cryptgraphy (PyPI)

MAL-2026-14388

Immediate action

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

pip uninstall cryptgraphy

What this malware does

The package impersonates the cryptography/boto3 ecosystem via a typosquatted name and falsified metadata (author 'AWS Support Team' [email protected], url https://aws.amazon.com/, module docstring 'botoo3 - Utilidades para AWS'). Its setup.py registers a CustomInstall command that runs automatically on pip install. The install hook writes a shell script to /tmp that sleeps for five minutes, then downloads an ELF binary from https://file.freestorage-04.bond/files/2026/8/23/10fef88e-73a5-4262-90b8-6585724390e6/boto3_utils.elf via curl/wget, stages it to /tmp/systemd-helper, chmods it executable, and launches it detached with nohup. The shipped Python module is a stub of no-op functions, so the only functional behavior on install is fetching and executing the opaque binary from an anonymous.bond host unrelated to any AWS or cryptography publisher. The delayed execution and systemd-mimicking filename are anti-forensics.

During installation package downloads and executes an executable. The remote executable appears to be broken but suggests intentions for persistence via systemd services, cryptocurrency mining and propagating over the network. Campaign shows some similarities with 2026-08-boto4

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

Campaign: 2026-08-mlflow-otel-instrumentor

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote executable.
worm
persistence
network-scan
cryptominer

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d303a7fa6aef47387f6029dfeb62ce66dd3231c0b0f77fc3611a65d53fc23a1a

ad7f362d84083dd8b3398e66da8abc40aecb79fd1d7b1b42d32938f9089bd3d2

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 cryptgraphy (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 cryptgraphy across your stack and pipelines.
If you installed it — respond
cryptgraphy 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 cryptgraphy 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 cryptgraphy 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. cryptgraphy 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

2026-08-mlflow-otel-instrumentorIN-MAL-2026-018593

References

Credits

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

Detect & block this

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