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

chai-as-hashednpm

Malicious code in chai-as-hashed (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-564
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall chai-as-hashed

What this malware does

The package chai-as-hashed 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.

Malicious versions

1 flagged
2.3.4

Indicators of compromise (SHA-256)

0f0e1b090cb9db7ad2687185748d227939549417c35f6cf08d5ec1e7c001b37b
f41b3bfa5c5bc9d3d747e0e36e6ac8139a2735004b33987b7c3706562f0a0246
350c5c25a5f848e40bd6e62ac9604b72364c8c8fbdd4e407a4fef18f386b9a83

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

  2. If you installed it — respond

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

Campaign

GHSA-xq26-9mh8-r598RLMA-2026-01150

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks chai-as-hashed-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.

chai-as-hashed (npm) malicious package — MAL-2026-564 | O3 Security