Which versions of graphrix are malicious?

The following npm versions of graphrix are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate graphrix if I installed it?

Remove graphrix from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed graphrix — how do I know if it already compromised me?

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

Yes — graphrix is associated with the GHSA-257q-hjm7-v3pp, RLMA-2026-01338, RLUA-2026-01966 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 graphrix 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 graphrix (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphrix across your stack and pipelines.

Malicious package

graphrixnpm

Malicious code in graphrix (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-692

Immediate action

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

npm uninstall graphrix

What this malware does

The package graphrix was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

88b6625fcbb125b7b3432974b307d94dfbe798496eb8285a739807f9d4b413a2

999c8394a8d5c821b17e5e5574f8d881c1281de19cc1df8af7f5dc82efe8a57f

f84c1fa1a2a58d1ff735a290b35059baec852170db47aa4c2674b84b896d4a90

4eb4fef754ed877e822a147e28893574f6b557861b483753a9366c45c4e4c90f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for graphrix (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphrix across your stack and pipelines.
If you installed it — respond
Remove graphrix from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If graphrix 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 graphrix 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. graphrix on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-257q-hjm7-v3ppRLMA-2026-01338RLUA-2026-01966

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks graphrix-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring