What does the jsondatatoruby malware do?

The package jsondatatoruby was found to contain malicious code. The OpenSSF Package Analysis project identified 'jsondatatoruby' @ 1.999.10 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of jsondatatoruby are malicious?

The following npm versions of jsondatatoruby are flagged malicious: 1.999.1, 1.999.10. Treat any of these as compromised.

How do I remediate jsondatatoruby if I installed it?

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

If jsondatatoruby was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find jsondatatoruby across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jsondatatoruby (2 malicious versions).

Malicious package

jsondatatorubynpm

Advisory published Dec 16, 2025Updated Dec 22, 2025

jsondatatoruby is a confirmed malicious npm package (MAL-2025-192584) that executes malicious code on install (malicious versions 1.999.1, 1.999.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jsondatatoruby (npm)

MAL-2025-192584

Immediate action

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

npm uninstall jsondatatoruby

What this malware does

The package jsondatatoruby was found to contain malicious code.

The OpenSSF Package Analysis project identified 'jsondatatoruby' @ 1.999.10 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.999.11.999.10

Indicators of compromise (SHA-256)

c436b35ef1446ad3a12861a0113e8d292919735fb107496429cac2f3287a8c32

baeae2c02ab89a72cdfb758215138d1c6ec321ee3c17535b0f2cbe54a341784d

89f78392e9a3a510c3e509f058c49aff59b8b98fff6beca0f5f30bbb8e85a9bd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for jsondatatoruby (2 malicious versions).
If you installed it — respond
Remove jsondatatoruby 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 jsondatatoruby was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. jsondatatoruby on npm has been identified as a malicious package (versions 1.999.1, 1.999.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks jsondatatoruby-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