What does the graphicsx malware do?

Installing the package starts downloading and installing an Infostealer Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2024-12-graphicsx Reasons (based on the campaign): - The package overrides the install command in setup.py to execute malicious code during installation. - obfuscation - Downloads and executes a remote executable. - infostealer - exfiltration-browser-data

Which versions of graphicsx are malicious?

The following PyPI versions of graphicsx are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate graphicsx if I installed it?

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

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

Yes — graphicsx is associated with the RLMA-2025-00470, 2024-12-graphicsx, RLUA-2026-00366 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 graphicsx 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 graphicsx (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphicsx across your stack and pipelines.

Malicious package

graphicsxPyPI

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

MAL-2025-931

Immediate action

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

pip uninstall graphicsx

What this malware does

Installing the package starts downloading and installing an Infostealer

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

Campaign: 2024-12-graphicsx

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation
Downloads and executes a remote executable.
infostealer
exfiltration-browser-data

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

e7c23483fc057cbabf1eab75be2079c19be4fd0d59acc589c7e10f6e1aaae9fd

72bbd36a189b910a0d14dfacb8bb7b559a8833737f1ef6c5645acaa823a6f1de

3f85a722af04dc8f110fe530c6c3de3345ac2cf99b4e315d82cbbf0039c54660

1b9a7a12b659cb9c2c5dd7f2bf3fcd5223252f4e4c7a00ea93039a0e6f27bcef

1145f1cef51eb38de2596142c23573dfa9a127494111dcff232dfac99f0a7c6c

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

Campaign

RLMA-2025-004702024-12-graphicsxRLUA-2026-00366

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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