Which versions of graphhub are malicious?

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

How do I remediate graphhub if I installed it?

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

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

Yes — graphhub is associated with the GHSA-g6qp-379w-2jrw, RLMA-2025-05807, RLUA-2025-06360, RLUA-2026-01960 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 graphhub 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 graphhub (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphhub across your stack and pipelines.

Malicious package

graphhubnpm

graphhub is a confirmed malicious npm package (MAL-2025-55018) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in graphhub (npm)

MAL-2025-55018

Immediate action

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

npm uninstall graphhub

What this malware does

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

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

4b0d6ee11320721cc3e65d9887c3b251b574bc7e67419fe63dedaa18b15dad9b

e2f3f531a91594ad386dc82c959af2f53b1e335972b4a7a451fe0184252616c3

14c8c3461d625fb2ecf5ac1d1404ef36965eb422732852251bfb4ee5fd0e400b

c370f6718c5470e7938eaa2c21a87b1806dd1a5427bfb3ae35882de427c7ac62

a32ff56e643c6dee794b4d27ae491c938bee336d5cb5e6a3fe86f4bb70786ee8

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

Campaign

GHSA-g6qp-379w-2jrwRLMA-2025-05807RLUA-2025-06360RLUA-2026-01960

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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