Which versions of ai-cypher are malicious?

The following PyPI versions of ai-cypher are flagged malicious: 0.1.0, 0.2.0. Treat any of these as compromised.

How do I remediate ai-cypher if I installed it?

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

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

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

Malicious package

ai-cypherPyPI

Malicious code in ai-cypher (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-192683

Immediate action

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

pip uninstall ai-cypher

What this malware does

The compiled native extension hides the code that during import exfiltrates sensitive Telegram files.

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

Campaign: 2025-12-ai-cypher

Reasons (based on the campaign):

exfiltration-credentials
target:telegram
native-extension

Malicious versions

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

5484d32cf20d26ce1585cb1cf90d2ed28c9cf9ccdcf038976a5cec33dd939e4d

9de254a4cdc670cee76e5c49607884a99d31121b414e16e87be441163c0c114f

7c88a021ffc1e8d7e717f4c1fdce1017fcb18af9f5581961f75c8d2b0145d10b

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

Campaign

2025-12-ai-cypher

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks ai-cypher-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