Which versions of graphbase-js are malicious?

The following npm versions of graphbase-js are flagged malicious: 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.2.0, 2.2.1. Treat any of these as compromised.

How do I remediate graphbase-js if I installed it?

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

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

Yes — graphbase-js is associated with the GHSA-29w9-hfv4-jjxh, RLMA-2026-05107, RLUA-2026-05550 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 graphbase-js 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 graphbase-js (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphbase-js across your stack and pipelines.

Malicious package

graphbase-jsnpm

Malicious code in graphbase-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5502

Immediate action

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

npm uninstall graphbase-js

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

6 flagged

2.1.32.1.42.1.52.1.62.2.02.2.1

Indicators of compromise (SHA-256)

bcdb883b3cbdcf4216f99f55d52d1b93db24271ddcf4a1e232f444a75709f76a

d609b37edc3b0517433f960677528b6b821a74c019639c1ba85568de9af92ca5

15b11d09b7491a9bd7fb602add8606aea4ddfc9d2499aed4d9836b75161df116

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

Campaign

GHSA-29w9-hfv4-jjxhRLMA-2026-05107RLUA-2026-05550

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks graphbase-js-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