Which versions of graph-dynamic are malicious?

The following npm versions of graph-dynamic are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate graph-dynamic if I installed it?

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

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

Yes — graph-dynamic is associated with the GHSA-6q72-5cph-5xxf, RLMA-2026-01335, RLUA-2026-01767 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 graph-dynamic 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 graph-dynamic (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graph-dynamic across your stack and pipelines.

Malicious package

graph-dynamicnpm

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

MAL-2026-1177

Immediate action

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

npm uninstall graph-dynamic

What this malware does

The package graph-dynamic 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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

2662ddb0770767495266ae6388242dbeb6fd0dfde8015252228968e4d28e1ad1

8fc9e411d29d7d359cf81fe3140dc3cee9d1583e20ad8bbf32ca9fb9e6e09860

33f8e989dcf03df5d69d406b9e3eb4670720e94b9f14d0366b34d02fd829c388

66b6dc8bb56813a8d9b4043c10b72f6abeb416fb82d1b8f01751b86909d9851a

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

Campaign

GHSA-6q72-5cph-5xxfRLMA-2026-01335RLUA-2026-01767

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks graph-dynamic-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