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

raven-hubspotnpm

Malicious code in raven-hubspot (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192597
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall raven-hubspot

What this malware does

The package raven-hubspot 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.

The OpenSSF Package Analysis project identified 'raven-hubspot' @ 20.0.0 (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

1 flagged
20.0.0

Indicators of compromise (SHA-256)

237fc455ae27b6e8e78e670a89354b6ad8c3d19e9abd2050218e33baba96ff45
6f62a48e9794e44ec492f8e1951f61f7953e08d5217b220ebcdea64d076a9d57
273a299e42e423bb2ac50f586ff57f8e869843110509c6d0e50b62dd9e91c228

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 raven-hubspot (version 20.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging raven-hubspot across your stack and pipelines.

  2. If you installed it — respond

    Remove raven-hubspot 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 raven-hubspot 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 raven-hubspot 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. raven-hubspot on npm has been identified as a malicious package (version 20.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wggj-3c6j-49w5

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks raven-hubspot-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.

raven-hubspot (npm) malicious package — MAL-2025-192597 | O3 Security