Which versions of graphnet are malicious?

The following npm versions of graphnet are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8. Treat any of these as compromised.

How do I remediate graphnet if I installed it?

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

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

Yes — graphnet is associated with the GHSA-gpj4-x5qp-hvrr, RLMA-2025-05808, RLUA-2026-01963 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 graphnet 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 graphnet (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphnet across your stack and pipelines.

Malicious package

graphnetnpm

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

Malicious code in graphnet (npm)

MAL-2025-48929

Immediate action

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

npm uninstall graphnet

What this malware does

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

8 flagged

0.0.10.0.20.0.30.0.40.0.50.0.60.0.70.0.8

Indicators of compromise (SHA-256)

f027c14837595ab3595469caa7197e8cdf4f3288a53a4c1fbf970cbb7cd6018d

022ef4190a3153420248771034a085983347a98a7bbd3be8ce4eaf80b0d0dfd8

a6686e3ad6418db34a6399abd97425d826a1f8087f9676ec16fa859618290771

2b2e92423ace48497f8fb11e282c9bdb510b37c639b8d417d05ce82c53be4293

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

Campaign

GHSA-gpj4-x5qp-hvrrRLMA-2025-05808RLUA-2026-01963

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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