Which versions of anaylze-json are malicious?

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

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

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

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

Yes — anaylze-json is associated with the GHSA-wjgw-rm6m-wgr3, RLMA-2026-04832, RLUA-2026-05494 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 anaylze-json 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 anaylze-json (version 3.10.14). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging anaylze-json across your stack and pipelines.

Malicious package

anaylze-jsonnpm

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

MAL-2026-5505

Immediate action

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

npm uninstall anaylze-json

What this malware does

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

1 flagged

3.10.14

Indicators of compromise (SHA-256)

7a24ff6c7af790535067ae83e9bba9a3b741da26221ac8738911ed6a8fc0aa24

bf569831fc9bbd326cf4ee10892c0e885fc03a98a35d398c68679c4956f78afb

6a61327c91aab23e4e576867e53bdafed9d721e62de6dad6fab34c0c0c80048e

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

Campaign

GHSA-wjgw-rm6m-wgr3RLMA-2026-04832RLUA-2026-05494

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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