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

chai-as-validatednpm

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

MAL-2025-192724
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall chai-as-validated

What this malware does

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

Indicators of compromise (SHA-256)

2c9381cc8f5a51ff293e1e8b16e8bde383379b7ed751b9700f7a54b9df7bf798
ac732b7c822ce779d3d7579dba60aef4d3d11aadbd5ee31db0eab0e240833634
d72b52e278b0d88eca8e67015e29d5eef13d699a7cdd07b75670b3e6755306c3
1f926a771e373aa8d47570130031dd1984d43b35230ba84d1837425e8929a20d

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

  2. If you installed it — respond

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

Campaign

RLMA-2025-06085GHSA-xhmc-g8hp-fgqqRLUA-2026-01161

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks chai-as-validated-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-validated (npm) malicious package — MAL-2025-192724 | O3 Security