Which versions of json-panels are malicious?

The following npm versions of json-panels are flagged malicious: 2.3.8. Treat any of these as compromised.

How do I remediate json-panels if I installed it?

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

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

Yes — json-panels is associated with the RLMA-2025-06373, RLUA-2026-01369 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 json-panels 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 json-panels (version 2.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-panels across your stack and pipelines.

Malicious package

json-panelsnpm

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

MAL-2025-192807

Immediate action

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

npm uninstall json-panels

What this malware does

The package json-panels was found to contain malicious code.

Malicious versions

1 flagged

2.3.8

Indicators of compromise (SHA-256)

0e04e573986a8a72253ff7643f91f06cf874750dec4c4844b91d4289d291a095

14bb299cb1e56d4f7b4d57f302ae1b026008c1774c15d82f34339ce9aca711da

633bb023c0cf1b32535a5c4c905709bc42ae60866046dbf77b61f9106ee934ff

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

Campaign

RLMA-2025-06373RLUA-2026-01369

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks json-panels-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