Which versions of graphflowx are malicious?

The following npm versions of graphflowx are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate graphflowx if I installed it?

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

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

Yes — graphflowx is associated with the GHSA-8jpg-855v-mh37, RLMA-2026-01337, RLUA-2026-01958 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 graphflowx 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 graphflowx (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphflowx across your stack and pipelines.

Malicious package

graphflowxnpm

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

MAL-2026-834

Immediate action

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

npm uninstall graphflowx

What this malware does

The package graphflowx 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

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

d297a9f3d4e974972015d3869473fee386c696410e1746be7088d2ad5d0bf69e

f4266b530d4c7c33d31f0b615033dac2a3a57218c537f1d13449342f0fbbc29b

1d02cf92f86da87ed1db4577dbe513e1dcf664350a8f056abc54aecc76b73c7c

72118517bad64d871f542eccad4ed5720699e93bf41dfe7ed9cf940e02ea8e56

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

Campaign

GHSA-8jpg-855v-mh37RLMA-2026-01337RLUA-2026-01958

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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