Which versions of cryptograohy are malicious?

The following PyPI versions of cryptograohy are flagged malicious: 0.5.6, 0.5.7, 0.5.8, 0.5.9, 0.6.0, 0.6.1, 0.6.2, 0.6.3, 0.6.4, 0.6.5, 0.6.6, 0.6.7, 0.7.0, 0.7.1. Treat any of these as compromised.

How do I remediate cryptograohy if I installed it?

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

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

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

Malicious package

cryptograohyPyPI

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

MAL-2024-11568

Immediate action

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

pip uninstall cryptograohy

What this malware does

The pyprettifier library has a feature to send out the user home path throuh the logger. It's attached to the init of EmojiConverter class. Other related packages utilize a typosquatting to imitate real packages, and attempts to call the EmojiConverter from pyprettifier, triggering notifying the author about the user's home path.

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: 2024-09-pyprettifier

Reasons (based on the campaign):

typosquatting
The malicious code is intentionally included in a dependency of the package
action-hidden-in-lib-usage
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

The OpenSSF Package Analysis project identified 'cryptograohy' @ 0.5.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

14 flagged

0.5.60.5.70.5.80.5.90.6.00.6.10.6.20.6.30.6.40.6.50.6.60.6.70.7.00.7.1

Indicators of compromise (SHA-256)

46fc867d84bea76cc43b2bc729531ba57bdfb586a25cbdff404caa24e3f0d674

69c9f05e42e277434eb37e4dddb268f3144eb27cb1de261c86cd396f7b1c9d14

69e5da8ec251eaf24472965979e51ce587019e7cde56a6ffd843c2387bedf8ce

717efeef381f3586a0dd564a02156268a92ede80a1bc5cfe1edaba25483dd33f

cd6f74fb7bf003f9463b7227a7f0ec3aa3886f74e8c1ff672b743a0cbaead2bd

d7f15e3d41fac09e705cca6a4c954dd7cb326e99262f071cfe963fad67fef9f8

ad05bc469f2afceb4046e1ab45b836e84a607b79bb0d8f10c520e21734340c23

67095679f8af3205e005b17a996da2ba17789715d7c66e4fcf31d8c387b85c00

277ab1c1f29ca50b242c7deed7e534c059ccce52681cb5278f02f68f9da64dfc

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 cryptograohy (14 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cryptograohy across your stack and pipelines.
If you installed it — respond
cryptograohy 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 cryptograohy 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 cryptograohy 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. cryptograohy on PyPI has been identified as a malicious package (versions 0.5.6, 0.5.7, 0.5.8, 0.5.9, 0.6.0, 0.6.1, 0.6.2, 0.6.3, and 6 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-110162024-09-pyprettifier

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

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