Which versions of pycryptographylibv3 are malicious?

The following PyPI versions of pycryptographylibv3 are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate pycryptographylibv3 if I installed it?

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

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

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

Malicious package

pycryptographylibv3PyPI

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

MAL-2024-12330

Immediate action

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

pip uninstall pycryptographylibv3

What this malware does

Importing the module starts an infostealer

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

Campaign: 2023-12-bananasquad

Reasons (based on the campaign):

infostealer
exfiltration-browser-data
exfiltration-generic

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

4dbf6d8d4cb6373e95302f0d85a8da4618c96ad08d298955d1de389bcfb85214

961e4f12709e7f7b2cceaca041246d901647f258e22b2930e53a181dbe0c52ef

ce5d3cccce83214270e0b604eafabe76957a64a51b6506e63d6292d484dac8aa

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

Campaign

2023-12-bananasquad

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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