Which versions of json-lucide are malicious?

The following npm versions of json-lucide are flagged malicious: 1.0.3, 1.0.4, 1.0.5, 1.0.7, 1.0.8. Treat any of these as compromised.

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

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

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

Yes — json-lucide is associated with the GHSA-7x8p-2g3v-pwqp, RLMA-2026-01979 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-lucide 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-lucide (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-lucide across your stack and pipelines.

Malicious package

json-lucidenpm

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

MAL-2026-2200

Immediate action

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

npm uninstall json-lucide

What this malware does

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

5 flagged

1.0.31.0.41.0.51.0.71.0.8

Indicators of compromise (SHA-256)

30298bc83e4bdadd246cfdec7006f865348448a5147e0a8258cd4d4feaf7b27f

12d05056fbe7eca08a66d7297aac2b03763073361f0cb33c238a4463f64a0867

a7f1fea723b06e0eba8237a1f539c23e5e97c4ae2a95d4e4bc4b5eb7907a4323

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

Campaign

GHSA-7x8p-2g3v-pwqpRLMA-2026-01979

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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