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

zohocrm-nodejs-sdk-3.0npm

zohocrm-nodejs-sdk-3.0 is a confirmed malicious npm package (MAL-2025-49079) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zohocrm-nodejs-sdk-3.0 (npm)

MAL-2025-49079
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall zohocrm-nodejs-sdk-3.0

What this malware does

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 installs a dependency hosted on a custom domain that runs an info stealer during installation. The info stealer focuses on stealing npm, git, and other CI/CD related tokens.

Malicious versions

1 flagged
99.0.0

Indicators of compromise (SHA-256)

8667273dd1820eda9a1a67abda3359d484492251a23ee3bb7acb310721b92ed5
249866d4162849dbcfaf86edff04913ac3fc074fa1f698951cb8c6e9f53b4e9b
dea2804610c201864e956319a58abd2c43d237fc38b8cf1065b66f9b8bd18b3c

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    zohocrm-nodejs-sdk-3.0 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.

  3. Did it already run?

    If zohocrm-nodejs-sdk-3.0 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 zohocrm-nodejs-sdk-3.0 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. zohocrm-nodejs-sdk-3.0 on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jp96-hc4j-6xx2RLMA-2025-06010

References

Credits

  • ReversingLabs · finder

Detect & block this

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

Explore

zohocrm-nodejs-sdk-3.0 (npm) malicious package — MAL-2025-49079 | O3 Security