Which versions of graphkitx are malicious?

The following npm versions of graphkitx are flagged malicious: 2.0.0, 2.1.0. Treat any of these as compromised.

How do I remediate graphkitx if I installed it?

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

If graphkitx was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is graphkitx part of a known attack campaign?

Yes — graphkitx is associated with the RLMA-2025-04548, RLUA-2026-01961 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 graphkitx across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for graphkitx (2 malicious versions).

Malicious package

graphkitxnpm

Advisory published Aug 28, 2025Updated Apr 16, 2026

graphkitx is a confirmed malicious npm package (MAL-2025-41572) that executes malicious code on install (malicious versions 2.0.0, 2.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in graphkitx (npm)

MAL-2025-41572

Immediate action

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

npm uninstall graphkitx

Malicious versions

2 flagged

2.0.02.1.0

Indicators of compromise (SHA-256)

4bab0b12e99a9b231eeb18b9b3cd476a1727f040b5d02535559b8d3d0c28258f

abeaef3781404f150f6fc6d94af571dd6039d107cf775b6b390b5fde065de496

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for graphkitx (2 malicious versions).
If you installed it — respond
Remove graphkitx 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 graphkitx was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. graphkitx on npm has been identified as a malicious package (versions 2.0.0, 2.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04548RLUA-2026-01961

References

reversinglabs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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