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

chai-as-proofednpm

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

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

What this malware does

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

Indicators of compromise (SHA-256)

b69ea2b92d530f84e379af75eaaefcf70c71f603a5bb307eb7e658b4b290db8d
2f83db1fa5312f0e34beebb192fb972f2d0e88650b49945571b438d27156de06
0fca2ccb93aa6609a9d7b9b5eb56cde7b36be5bb1d1b051c18e4dd724725b81b
2355fe049fdbb7e74d2edb113b364063cbdae3dc311d476efd426e8d5efe7c35

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-proofed (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-proofed across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

GHSA-8g87-54x4-gfx2RLMA-2026-01155RLUA-2026-01722

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

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