Which versions of deepseek-api are malicious?

The following PyPI versions of deepseek-api are flagged malicious: 0.5.3, 0.5.3.1. Treat any of these as compromised.

How do I remediate deepseek-api if I installed it?

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

If deepseek-api was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is deepseek-api part of a known attack campaign?

Yes — deepseek-api is associated with the 2024-07-adfboba 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 deepseek-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for deepseek-api (2 malicious versions).

Malicious package

deepseek-apiPyPI

Advisory published Jul 9, 2024Updated Dec 31, 2025

deepseek-api is a confirmed malicious PyPI package (MAL-2024-12251) that steals credentials and exfiltrates sensitive data (malicious versions 0.5.3, 0.5.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in deepseek-api (PyPI)

MAL-2024-12251

Immediate action

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

pip uninstall deepseek-api

What this malware does

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

Campaign: 2024-07-adfboba

Reasons (based on the campaign):

Malicious versions

2 flagged

0.5.30.5.3.1

Indicators of compromise (SHA-256)

3e0f946cc93560dc8afa6a2bd21652b57fd6bd63f8d7265edd9a9aa3e1225e41

96ca6d620b3741a6c0d3df99b09223e35e63a15cf8dcc5935d28785ad66361b0

1a9ead576c318549eaad35c36a6a1ca48e821f0b3efddfd509261a1dbcf9b1ab

15348d95d77903e959b6635899dd19debf6327b153cb179245f1c3a45d1a5cf8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for deepseek-api (2 malicious versions).
If you installed it — respond
deepseek-api 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 deepseek-api was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. deepseek-api on PyPI has been identified as a malicious package (versions 0.5.3, 0.5.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-07-adfboba

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks deepseek-api-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

Explore

All malware advisories How O3 detects malware Vulnerability database