Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

jsondatatorubynpm

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

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
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jsondatatoruby (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsondatatoruby across your stack and pipelines.

  2. 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.

  3. Did it already run?

    If jsondatatoruby 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.

  4. How O3 protects you

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

jsondatatoruby (npm) malicious package — MAL-2025-192584 | O3 Security