Which versions of jsonsurge are malicious?

The following npm versions of jsonsurge are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate jsonsurge if I installed it?

jsonsurge is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed jsonsurge — how do I know if it already compromised me?

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

Yes — jsonsurge is associated with the GHSA-4gh2-4gxh-wxwx 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 jsonsurge 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 jsonsurge (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonsurge across your stack and pipelines.

Malicious package

jsonsurgenpm

Malicious code in jsonsurge (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191114

Immediate action

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

npm uninstall jsonsurge

What this malware does

The package jsonsurge 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

ea90622d26555bede79ddb66877dfab50d3ff9cdb92fc4d8dbf1a8bd2c9d8497

3be25933730aa193fff2d8a76c8c77280080a4638998b7aa754cc9909cacdd34

09d795548cfda390ad25d33a8e7ce0d115cf76f9c2e6dedcb8459e15d41a2c72

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jsonsurge (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonsurge across your stack and pipelines.
If you installed it — respond
jsonsurge is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If jsonsurge 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 jsonsurge 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. jsonsurge on npm has been identified as a malicious package (version 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4gh2-4gxh-wxwx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks jsonsurge-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring