Which versions of json-specular are malicious?

The following npm versions of json-specular are flagged malicious: 7.4.11, 7.4.12. Treat any of these as compromised.

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

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

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

Yes — json-specular is associated with the GHSA-gmvg-736c-7g9f, RLMA-2026-01777, RLUA-2026-01980 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-specular 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-specular (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-specular across your stack and pipelines.

Malicious package

json-specularnpm

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

MAL-2026-1978

Immediate action

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

npm uninstall json-specular

What this malware does

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

2 flagged

7.4.117.4.12

Indicators of compromise (SHA-256)

1bb4124a4b5522f2d7f36098f59a85a760b3e029a30baffafa922a34d2e7a21c

21e4ef994911ed1494838bbc4c0f20fb4e194a7e264a9e7014759d9e23466ac9

8a04df808b181af308ba610ae94abc9d0fbd0c9cfd30ff73698a179ee34f0b32

5caa3684930a3a59a86c4fbd51f4e40c81b9cebd0190606a5498c33cfae83dcd

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

Campaign

GHSA-gmvg-736c-7g9fRLMA-2026-01777RLUA-2026-01980

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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