What does the intgraphx 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 intgraphx are malicious?

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

How do I remediate intgraphx if I installed it?

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

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

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

Malicious package

intgraphxPyPI

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

MAL-2025-936

Immediate action

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

pip uninstall intgraphx

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)

1d0358aaf573ea9d5800068018a195abc017e030fb094e87b2a4c526db595eb8

f832face91cb3bc59a9a4058595280e472063b084048058b6151ab55920f5a6d

4fb1e216d0815e75bd49620f6176c757576a58b8e4669df0ff803d7a84aad2ba

636f329e6b57f489d7a996b5c655e99c9d8a3152b5df9c345a4a3df4452b456e

14fe2aa49ceea8af099423e5df6b3dedea3b36a6cc17abcc5e7d7b6b4ac16db2

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 intgraphx (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging intgraphx across your stack and pipelines.
If you installed it — respond
intgraphx 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 intgraphx 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 intgraphx 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. intgraphx 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-004762024-12-graphicsxRLUA-2026-00430

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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