Which versions of zircuit-reporter are malicious?

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

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

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

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

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

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

Malicious package

zircuit-reporternpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

zircuit-reporter is a confirmed malicious npm package (MAL-2026-7445) 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-reporter (npm)

MAL-2026-7445

Immediate action

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

npm uninstall zircuit-reporter

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

6e0204a25df9ceda8e2a7a709c32f7028c3ada997317f7be7d5c1c2366ffb715

856787fe3874a95dbb654121bc383616a38dc4273b5694adf3a1b8d229b95594

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zircuit-reporter (version 99.0.0).
If you installed it — respond
Remove zircuit-reporter 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-reporter 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-reporter 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-05381RLUA-2026-06564

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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