Which versions of @tiaanduplessis/json are malicious?

The following npm versions of @tiaanduplessis/json are flagged malicious: 2.0.2, 2.0.3. Treat any of these as compromised.

How do I remediate @tiaanduplessis/json if I installed it?

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

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

Yes — @tiaanduplessis/json is associated with the GHSA-7qf3-m8rp-vq57 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 @tiaanduplessis/json 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 @tiaanduplessis/json (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @tiaanduplessis/json across your stack and pipelines.

Malicious package

@tiaanduplessis/jsonnpm

Malicious code in @tiaanduplessis/json (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191056

Immediate action

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

npm uninstall @tiaanduplessis/json

What this malware does

The package @tiaanduplessis/json 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

2 flagged

2.0.22.0.3

Indicators of compromise (SHA-256)

09169ec1c754891fb711632f82fddd2aefa9407fedb8048ee15cb8678e78aaff

168863978d57f795dd22cad8078c613f3fc927228b5f68e5b48b0d488e409d09

934994d3e44c6f137b7d0404fd662535084e2d850c94c0e0b421330d773e560a

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

Campaign

GHSA-7qf3-m8rp-vq57

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @tiaanduplessis/json-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