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

chai-as-enhancednpm

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

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

What this malware does

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

3 flagged
4.2.84.3.04.3.2

Indicators of compromise (SHA-256)

cb4ee9056898577e40bbef5e13e321597457852aa84f71886d4aef75898669aa
7fb34c187e4750d1e5a6dc3c297a953d8089f054d74e4cac7667532d81b72ea8
fdf6ddfded1a70a4a5b5731423f38360350c716d199a92f9e7f6cd439adb6775

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

  2. If you installed it — respond

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

Campaign

GHSA-5572-pgc4-7mjfRLMA-2026-01147

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks chai-as-enhanced-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-enhanced (npm) malicious package — MAL-2026-239 | O3 Security