Which versions of jsonjoy.com are malicious?

The following npm versions of jsonjoy.com are flagged malicious: 20.1.1. Treat any of these as compromised.

How do I remediate jsonjoy.com if I installed it?

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

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

Yes — jsonjoy.com is associated with the GHSA-hgm9-h5c3-3gww, RLMA-2025-05049, RLUA-2026-01377 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 jsonjoy.com 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 jsonjoy.com (version 20.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonjoy.com across your stack and pipelines.

Malicious package

jsonjoy.comnpm

jsonjoy.com is a confirmed malicious npm package (MAL-2025-47073) that executes malicious code on install (malicious version 20.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jsonjoy.com (npm)

MAL-2025-47073

Immediate action

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

npm uninstall jsonjoy.com

What this malware does

The package jsonjoy.com 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

1 flagged

20.1.1

Indicators of compromise (SHA-256)

84ed9a921baae45f95050be87e9143e6c63cde1254639e1a9e4a1eb768724f13

42d7445c0e30d8eeedead15fb14cfbfeeaf794d4515195ab8ff4526bff58efc7

02aa63ce49c4c0c2721291e599b0f010a1d1fa625fb5bc530ece11841c64319b

2f5a5b42fb66f3e5e1f5fba7172236bdd5f994fff0fb05ad1d5232537bdf4d5c

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

Campaign

GHSA-hgm9-h5c3-3gwwRLMA-2025-05049RLUA-2026-01377

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks jsonjoy.com-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

Explore

All malware advisories How O3 detects malware Vulnerability database