Which versions of graphicsctxr are malicious?

The following PyPI versions of graphicsctxr are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4, 2.1.1, 2.2.1, 2.2.2, 2.2.3. Treat any of these as compromised.

How do I remediate graphicsctxr if I installed it?

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

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

Yes — graphicsctxr is associated with the 2026-04-renderctx 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 graphicsctxr 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 graphicsctxr (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphicsctxr across your stack and pipelines.

Malicious package

graphicsctxrPyPI

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

MAL-2026-3210

Immediate action

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

pip uninstall graphicsctxr

What this malware does

Package contains code to exfiltrate .env to a remote target. Prior to version 2.1.1, it also created a persistent backdoor via embedding a hardcoded SSH key. Malicious action is triggered when running as a module.

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

Campaign: 2026-04-renderctx

Reasons (based on the campaign):

backdoor
files-exfiltration
crypto-related
The malicious code is intentionally included in a dependency of the package

Malicious versions

8 flagged

1.0.11.0.21.0.31.0.42.1.12.2.12.2.22.2.3

Indicators of compromise (SHA-256)

34bd28973c19fb216e480f592ebb72871a414aad3113095cc700641f1c30ec60

10408decaf8cace14b8124fa392ee96996c3c91358cb454cbfcd45790d18cdf9

b839d254c22132d7021df652975bb55f3592b26266146e6495881a98215e5a6d

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

Campaign

2026-04-renderctx

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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