Which versions of json-specparse are malicious?

The following npm versions of json-specparse are flagged malicious: 7.4.9, 7.4.10, 7.4.11. Treat any of these as compromised.

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

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

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

Yes — json-specparse is associated with the GHSA-w3m6-xffr-576m, RLMA-2026-01370, RLUA-2026-01776 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-specparse 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-specparse (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-specparse across your stack and pipelines.

Malicious package

json-specparsenpm

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

MAL-2026-1368

Immediate action

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

npm uninstall json-specparse

What this malware does

The package json-specparse 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

3 flagged

7.4.97.4.107.4.11

Indicators of compromise (SHA-256)

18627c1c0def6faaa8722de5bc97f27981110eaf8844500039b842de043d2f62

a9b7464a2349596a7884e9cc1a56354e6a9e24919a93e7de07fef14dd5c1b2af

28ad383c55884ea3f12626f13a56f36b7fbc1eab649de47cfcb657478162850c

7bb576eb060db82d26a3cd1314730ccd8eb4b228477c77fb46521798f3f542bd

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

Campaign

GHSA-w3m6-xffr-576mRLMA-2026-01370RLUA-2026-01776

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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