Which versions of cryptocalls are malicious?

The following PyPI versions of cryptocalls are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate cryptocalls if I installed it?

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

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

Yes — cryptocalls is associated with the RLMA-2024-11015, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00237 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 cryptocalls 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 cryptocalls (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 cryptocalls across your stack and pipelines.

Malicious package

cryptocallsPyPI

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

MAL-2024-11567

Immediate action

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

pip uninstall cryptocalls

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ceebd8f260e0e5df67c32a5aa401eb763ee73f5d54a8de236b5afa1a523dc7b4

64f2143770b4a9f8f3ba71a09bdbbba45b6ba0b14590c30c894cf049059a3d51

68c6992c85099024497d762301f8ae5ee3217a04bdcddff3d4f3ecc214bd737a

7d72d54a5eedc80b0ec67a845d61f254c95624118ccd836611e0f01ce60379bc

a2af34dfd5ee694d0a7e257069780664111878dc3240a7af7c89dc9ac86e9a73

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

RLMA-2024-110152024-08-embeds-RealtekHDAudioManagerRLUA-2026-00237

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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