Which versions of graphlib-js are malicious?

The following npm versions of graphlib-js are flagged malicious: 1.2.0, 1.2.1, 1.2.2, 1.3.2, 1.3.3, 1.3.4. Treat any of these as compromised.

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

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

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

Yes — graphlib-js is associated with the GHSA-mfcc-4344-rj22, RLMA-2026-01768, RLUA-2026-01962 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 graphlib-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 graphlib-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 graphlib-js across your stack and pipelines.

Malicious package

graphlib-jsnpm

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

MAL-2026-1491

Immediate action

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

npm uninstall graphlib-js

What this malware does

The package graphlib-js 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

6 flagged

1.2.01.2.11.2.21.3.21.3.31.3.4

Indicators of compromise (SHA-256)

375768659fc55b18acf652226fabd9052c10c4f88d36f150317532bc8661df13

6fc5e5e2ae1439a28be92e99758c3253bf2bd09a568712a5d0725553b4836eaf

ce223f922e09ab9d58be02edc25ae0b37c647df4a8ba844ce2092164e4657328

566c768a44b22de1c0da09b1473de91432a1bbb459fc7290bee1b693d8e31580

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 graphlib-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 graphlib-js across your stack and pipelines.
If you installed it — respond
Remove graphlib-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 graphlib-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 graphlib-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. graphlib-js on npm has been identified as a malicious package (versions 1.2.0, 1.2.1, 1.2.2, 1.3.2, 1.3.3, 1.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mfcc-4344-rj22RLMA-2026-01768RLUA-2026-01962

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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