Which versions of graphalgo are malicious?

The following npm versions of graphalgo are flagged malicious: 2.2.5-pre, 2.2.6, 2.2.7, 2.2.8, 2.2.9, 2.2.10, 2.2.11. Treat any of these as compromised.

How do I remediate graphalgo if I installed it?

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

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

Yes — graphalgo is associated with the GHSA-5w3m-75fx-323p, RLMA-2025-02781, RLUA-2026-01956 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 graphalgo 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 graphalgo (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphalgo across your stack and pipelines.

Malicious package

graphalgonpm

graphalgo is a confirmed malicious npm package (MAL-2025-3687) that executes malicious code on install (malicious versions 2.2.5-pre, 2.2.6, 2.2.7…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in graphalgo (npm)

MAL-2025-3687

Immediate action

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

npm uninstall graphalgo

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

7 flagged

2.2.5-pre2.2.62.2.72.2.82.2.92.2.102.2.11

Indicators of compromise (SHA-256)

d5d170316b7d69234c298baf1d1364ae3207e2f0774c87782a648d4c492920bc

b946f4e925281acc3f50daca66b5540f2ddb12c9ac05f43e0867b053f8fe0a8a

73da2075158a51840a4ce21af7d0a6a66f41418afaf09adcdebe658fc1f318a8

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

Campaign

GHSA-5w3m-75fx-323pRLMA-2025-02781RLUA-2026-01956

References

Credits

ReversingLabs · finder

Detect & block this

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