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

cx-contact-hub-libnpm

cx-contact-hub-lib is a confirmed malicious npm package (MAL-2025-48275) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cx-contact-hub-lib (npm)

MAL-2025-48275
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cx-contact-hub-lib

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.

Malicious versions

1 flagged
99.0.0

Indicators of compromise (SHA-256)

d222fffa14a9ecd04210f41c25dae1aa3fc12e1ad8ec172358786ae1c539475e
b0d516934de4fdfe8665f7347108589bec06bdd1299a3bd7ecea32b9411c530e
56f2469986be4af7fdaefe4d9eaf524b669a23c66a6abe6624cc7e3805ce3c2e

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 cx-contact-hub-lib (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 cx-contact-hub-lib across your stack and pipelines.

  2. If you installed it — respond

    Remove cx-contact-hub-lib 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 cx-contact-hub-lib 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 cx-contact-hub-lib 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. cx-contact-hub-lib 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-4gmr-7rvm-cf57RLMA-2025-05338RLUA-2025-05714

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks cx-contact-hub-lib-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.

Explore

cx-contact-hub-lib (npm) malicious package — MAL-2025-48275 | O3 Security