Which versions of graphorbit are malicious?

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

How do I remediate graphorbit if I installed it?

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

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

Yes — graphorbit is associated with the GHSA-xh3c-r5g9-cx2x, RLMA-2025-05384, RLUA-2025-05809, RLUA-2026-01965 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 graphorbit 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 graphorbit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphorbit across your stack and pipelines.

Malicious package

graphorbitnpm

graphorbit is a confirmed malicious npm package (MAL-2025-48400) 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 graphorbit (npm)

MAL-2025-48400

Immediate action

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

npm uninstall graphorbit

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

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

7e39cb6a782c7394e47a516577dd7696fc2db73d710cdd07e5ceec3dbc46c7af

706b727a8d66b04ea656793bb28d20abe82fdeccf2a99cc8cc99f3b854d2720a

6d46c7a423bb4a8b7c5fe9fe789f5e576a8175a87ff566c8b3bb1ccf0ab03dd4

8c316d53bb4c652328693911d9216b70d299ad61dfd6e5492ac106ebbc4a746c

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 graphorbit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphorbit across your stack and pipelines.
If you installed it — respond
Remove graphorbit 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 graphorbit 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 graphorbit 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. graphorbit 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-xh3c-r5g9-cx2xRLMA-2025-05384RLUA-2025-05809RLUA-2026-01965

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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