Which versions of blender-headless are malicious?

The following PyPI versions of blender-headless are flagged malicious: 9.99.9. Treat any of these as compromised.

How do I remediate blender-headless if I installed it?

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

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

Yes — blender-headless is associated with the IN-MAL-2026-022566, GENERIC-standard-pypi-install-pentest 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 blender-headless across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for blender-headless (version 9.99.9).

Malicious package

blender-headlessPyPI

Advisory published Nov 8, 2026Updated Nov 8, 2026

blender-headless is a confirmed malicious PyPI package (MAL-2026-18758) that steals credentials and exfiltrates sensitive data (malicious version 9.99.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in blender-headless (PyPI)

MAL-2026-18758

Immediate action

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

pip uninstall blender-headless

What this malware does

The sdist setup.py and the gcp_log_poc/init.py module both construct a DNS label of the form {install|import}-{random-id}.blender-headless-{platform.node()} as a subdomain of finaltests99.dssldrf.net and resolve it via socket.getaddrinfo. This leaks the installer's hostname and install/import event to the authoritative server for that domain over DNS, a channel that bypasses typical HTTP egress controls. The setup.py path runs during pip install of the sdist; the init.py path runs on every import gcp_log_poc in any Python process. The package has no build logic and no functionality matching its name — the shipped module name (gcp_log_poc) and the package name (blender-headless) are unrelated, and the module's only behavior is the DNS beacon.

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

9.99.9

Indicators of compromise (SHA-256)

7edaff2bd9abfea10a907cf99f87b444eee0c7ff54e88face42fe7c000d64775

da370fd492985ac15dcdcda2445fce49069d7a2b4cf62514806e36d589570fb6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for blender-headless (version 9.99.9).
If you installed it — respond
blender-headless 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 blender-headless 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. blender-headless on PyPI has been identified as a malicious package (version 9.99.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022566GENERIC-standard-pypi-install-pentest

References

Credits

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

Detect & block this

O3 blocks blender-headless-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