Which versions of deepseeek are malicious?

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

How do I remediate deepseeek if I installed it?

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

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

Yes — deepseeek is associated with the RLMA-2025-01210, GENERIC-standard-pypi-install-pentest, RLUA-2026-00254 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 deepseeek 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 deepseeek (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 deepseeek across your stack and pipelines.

Malicious package

deepseeekPyPI

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

MAL-2025-1970

Immediate action

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

pip uninstall deepseeek

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)

14047b7b8891a0511b1468e68a832cc31d9dc05e95da0fb862ec3839b721d4b7

ce0683c4a79abcceb6385efa2395ea55b96ff5a96dd9ed020629b795947707bb

c082504cf7395cf145005cfa91f4c01eb9a8e1deb7b75d61f0b85b8e529ebde4

c813b7d53c3105fccd9a5e9fd73e19858b4d602fa7ddffd3dd3059d91e9ea674

22f020f61ab85e6cec0588108f14e7c872973b593680cde2c177b8c835c75511

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 deepseeek (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 deepseeek across your stack and pipelines.
If you installed it — respond
deepseeek 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 deepseeek 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 deepseeek 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. deepseeek 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-01210GENERIC-standard-pypi-install-pentestRLUA-2026-00254

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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