Which versions of deepface-weight are malicious?

The following PyPI versions of deepface-weight are flagged malicious: 0.1.4. Treat any of these as compromised.

How do I remediate deepface-weight if I installed it?

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

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

Yes — deepface-weight is associated with the 2026-08-deepface-weights, IN-MAL-2026-018247 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 deepface-weight 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 deepface-weight (version 0.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deepface-weight across your stack and pipelines.

Malicious package

deepface-weightPyPI

deepface-weight is a confirmed malicious PyPI package (MAL-2026-14158) that steals credentials and exfiltrates sensitive data (malicious version 0.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in deepface-weight (PyPI)

MAL-2026-14158

Immediate action

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

pip uninstall deepface-weight

What this malware does

On import, deepface-weight spawns a daemon background thread that polls the installer's working directory for data/telethon_market_userbot.session for approximately 10 minutes and POSTs the file to a hardcoded webhook.site endpoint (https://webhook.site/d6ea9c5b-4a85-4e59-9397-2bb5f9407c87). Telethon session files contain live authentication material granting full access to the associated Telegram account. The exfiltration destination is bound to a variable literally named evil_server_url with a Russian-language comment identifying it as the attacker's server. The package name mimics the popular deepface ML library but ships no machine-learning code; author metadata is a placeholder (asdqwdasdqwdasd) with a disposable email at playboot.com.

During import, package exfiltrates the sensitive file with the Telegram session token.

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

Campaign: 2026-08-deepface-weights

Reasons (based on the campaign):

files-exfiltration
target:telegram

Malicious versions

1 flagged

0.1.4

Indicators of compromise (SHA-256)

92f87cc2da145e4ab765c912a3a9cfb36ed6e8d21231fd511aa032edcd4b3e2b

6808b9ae619e6cf9fdb59b52305e25b8e2fdb87167fbd78fae0ca6c1c07a5f1a

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

Campaign

2026-08-deepface-weightsIN-MAL-2026-018247

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks deepface-weight-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