Which versions of graphchain are malicious?

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

How do I remediate graphchain if I installed it?

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

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

Yes — graphchain is associated with the GHSA-p6r4-w63w-r5wx, RLMA-2025-05026, RLUA-2026-01336, RLUA-2026-01957 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 graphchain 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 graphchain (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 graphchain across your stack and pipelines.

Malicious package

graphchainnpm

graphchain is a confirmed malicious npm package (MAL-2025-47096) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in graphchain (npm)

MAL-2025-47096

Immediate action

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

npm uninstall graphchain

What this malware does

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)

0f74a555cfba6dedc51a937d8cf8c843437538581dea703284d1e872317263f3

976e0c6a7a4a2123b76a36e09d3a672e88c7c8037527f172790c22e5a17f65ba

37bab4c2ad38efea8de60f98291a636aedcbd8002dc824a8b29d849d0790a1ff

9ede41d80087b37fb041a77dcd463adc4d1fec97b5f840b7f759156553d6814c

8d77be83c3da123958aa5b15f4b0d992b938824f2c8676bacac444bad1d163f8

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 graphchain (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 graphchain across your stack and pipelines.
If you installed it — respond
Remove graphchain 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 graphchain 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 graphchain 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. graphchain 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-p6r4-w63w-r5wxRLMA-2025-05026RLUA-2026-01336RLUA-2026-01957

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database