Which versions of parsejson-pro are malicious?

The following npm versions of parsejson-pro are flagged malicious: 2.3.18. Treat any of these as compromised.

How do I remediate parsejson-pro if I installed it?

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

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

Yes — parsejson-pro is associated with the GHSA-cv8h-5j9m-x3rc, RLMA-2026-01804, RLUA-2026-02017 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 parsejson-pro 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 parsejson-pro (version 2.3.18). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging parsejson-pro across your stack and pipelines.

Malicious package

parsejson-pronpm

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

MAL-2026-1962

Immediate action

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

npm uninstall parsejson-pro

What this malware does

The package parsejson-pro was found to contain malicious code.

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

2.3.18

Indicators of compromise (SHA-256)

f2f105fb92bd66d0baadfb4bc605643a2eaff5cd51a4d565f82f61e4c0cb3a71

bee06fce3066f17a6400fc1800b42e5c53eeb9826bb9672cec6ad8ff65306807

fd7cd08f731142ea7e191fd2154f92c40f024f078b02e3313c69821afbb4cb16

2d110673875f311b5ca515ca336cbe3f9b9adb8c25f326af3d3eebf9fe4b90ed

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

Campaign

GHSA-cv8h-5j9m-x3rcRLMA-2026-01804RLUA-2026-02017

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks parsejson-pro-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