Which versions of deepseekai are malicious?

The following PyPI versions of deepseekai are flagged malicious: 0.0.8. Treat any of these as compromised.

How do I remediate deepseekai if I installed it?

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

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

Yes — deepseekai is associated with the RLMA-2025-01211, GENERIC-standard-pypi-install-pentest, RLUA-2026-00256 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 deepseekai 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 deepseekai (version 0.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deepseekai across your stack and pipelines.

Malicious package

deepseekaiPyPI

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

MAL-2025-1971

Immediate action

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

pip uninstall deepseekai

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.0.8

Indicators of compromise (SHA-256)

912f47a1b71487a796e28a0ae681cac7a1a75fa3a4aa21ad5a650b58f0f1d15d

5a2fe581fd96fca9aeebabf98acee2c4757f2b0b373680c1396e8d47436056ec

b2b16bcb5b1deabfe7fb03e6a512343457033cfb57c0e70062d400d001b4a949

05c43e705052a9b9393b9f1c56de1626a63616222a135c4fd47fa00b8ef34d91

ef02d037b585b7f791cf93f3da43a279f4bd4b84e3159d3e0de3d68547eec82f

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

Campaign

RLMA-2025-01211GENERIC-standard-pypi-install-pentestRLUA-2026-00256

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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