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

chai-as-reformednpm

chai-as-reformed is a confirmed malicious npm package (MAL-2026-13942) that typosquats a legitimate package to trick installs (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-reformed (npm)

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

What this malware does

The package impersonates chai-as-promised and copies its README from pino, but its exported middleware spawns a detached node lib/caller.js process. caller.js base64-decodes a hardcoded jsonstorage.net URL (concealed together with an x-secret-key header name/value as base64 literals in a synthetic process.env object decoded with atob), fetches the JSON response, and passes its cookie field to new Function.constructor("require", s)(require), executing attacker-controlled JavaScript in the host Node.js process with access to require. The remote payload is mutable and can be changed by the operator of the storage URL at any time.

Malicious versions

1 flagged
1.2.0

Indicators of compromise (SHA-256)

ae73388f2a877d421e53b37bdd36496a8048149ffe2e64a975e87c705f8b0e45

Detection & response playbook

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

  2. If you installed it — respond

    chai-as-reformed is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-as-reformed, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

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

Campaign

IN-MAL-2026-017655

References

Credits

  • Amazon Inspector · finder

Detect & block this

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