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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for deepseek-api (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deepseek-api across your stack and pipelines.

Malicious package

deepseek-apiPyPI

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for deepseek-api (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deepseek-api across your stack and pipelines.
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 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 deepseek-api 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. 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