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

chai-as-redeployednpm

chai-as-redeployed is a confirmed malicious npm package (MAL-2026-3165) that executes malicious code on install (malicious versions 3.5.7, 3.5.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-redeployed (npm)

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

What this malware does

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

2 flagged
3.5.73.5.8

Indicators of compromise (SHA-256)

8f5082757dd821f6007210491d9d235401290e32c1e1a207b75a1eea150f40cd
e2e2a156e4adadf2466c1ce0f0501539ea4bb3306edd9b2c97109326a9f94f3a
09445e08ab818be499cd0f331db6610740c7db1fc49097e45274b53e9c769829

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

  2. If you installed it — respond

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

Campaign

GHSA-4cp9-q8r9-2227RLMA-2026-04996

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

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

Explore

chai-as-redeployed (npm) malicious package — MAL-2026-3165 | O3 Security