Which versions of chai-as-format are malicious?

The following npm versions of chai-as-format are flagged malicious: 2.3.5. Treat any of these as compromised.

How do I remediate chai-as-format if I installed it?

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

I already installed chai-as-format — how do I know if it already compromised me?

If chai-as-format 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.

Is chai-as-format part of a known attack campaign?

Yes — chai-as-format is associated with the IN-MAL-2026-017271 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find chai-as-format across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-format (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-format across your stack and pipelines.

Malicious package

chai-as-formatnpm

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

Malicious code in chai-as-format (npm)

MAL-2026-13701

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall chai-as-format

What this malware does

The package's index.js unconditionally requires./lib/config, which is a ~4MB single-line file consisting of an obfuscator.io-style hex-encoded string array (23,953 entries) with rotate/decoder functions and heavy control-flow flattening. This obfuscated code executes at every require('chai-as-format') on the installer's machine. The package presents itself under the name chai-as-format but its README, LICENSE, docs, and lib/* content are copied from the unrelated pino logging framework (LICENSE cites pinojs/pino), while the package.json description references vulnerability management — the cover story does not match the shipped content. A multi-megabyte opaque decoder auto-loaded on import is not a legitimate config module; the shape is a trojan loader hidden behind an impersonation shell.

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

97806af0cd2e189771ef929999ea4b1812c7933b87dbaf2a2a9b7e6815bce36c

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-format (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-format across your stack and pipelines.
If you installed it — respond
chai-as-format is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-as-format, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If chai-as-format 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.
How O3 protects you
O3 blocks chai-as-format 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-format on npm has been identified as a malicious package (version 2.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017271

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database