Which versions of zircuit-keeper are malicious?

The following npm versions of zircuit-keeper are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate zircuit-keeper if I installed it?

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

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

Yes — zircuit-keeper is associated with the RLMA-2026-05379, RLUA-2026-06562 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 zircuit-keeper across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zircuit-keeper (version 99.0.0).

Malicious package

zircuit-keepernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

zircuit-keeper is a confirmed malicious npm package (MAL-2026-7443) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zircuit-keeper (npm)

MAL-2026-7443

Immediate action

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

npm uninstall zircuit-keeper

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

9866037aad54e79b717c07fc50f01bbc90366b977d1cf8ab88eed502de2e03f7

4f45922d4b536371a9658de2b1917a6daec84d6b38ffbd8695f41acd9eaeab4c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zircuit-keeper (version 99.0.0).
If you installed it — respond
Remove zircuit-keeper 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 zircuit-keeper 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. zircuit-keeper on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05379RLUA-2026-06562

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks zircuit-keeper-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