Which versions of chai-as-sleek are malicious?

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

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

chai-as-sleek is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-as-sleek, 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-sleek — how do I know if it already compromised me?

If chai-as-sleek 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-sleek part of a known attack campaign?

Yes — chai-as-sleek is associated with the IN-MAL-2026-019847 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-sleek 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-sleek (version 7.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-sleek across your stack and pipelines.

Malicious package

chai-as-sleeknpm

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

Malicious code in chai-as-sleek (npm)

MAL-2026-16077

Immediate action

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

npm uninstall chai-as-sleek

What this malware does

Package published as 'chai-as-sleek' impersonates the pino logger: README, LICENSE, docs/, and index.d.ts are copied verbatim from pino, while package.json description reads 'This document describes the management of vulnerabilities...' and the README also markets the package as a chai plugin. The main entrypoint index.js unconditionally executes require('./lib/config') at load time. lib/config.js is a single ~4 MB line of obfuscator.io-obfuscated JavaScript (23,868-entry rotated string array, decoder functions T and j, control-flow flattening, ~20k decoder-wrapper calls) with no configuration content. package.json declares axios ^1.10.0 as a runtime dependency, but no readable source file imports axios — the only reachable consumer of the HTTP client is the opaque blob in lib/config.js. Any consumer that imports 'chai-as-sleek' executes this hidden payload at require() time with outbound HTTP capability provisioned.

Malicious versions

1 flagged

7.1.2

Indicators of compromise (SHA-256)

782914cb65e0d30697eb54f50a4c5b740a3a53941abc185759e296c1d2ec8e9e

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-sleek (version 7.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-sleek across your stack and pipelines.
If you installed it — respond
chai-as-sleek is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-as-sleek, 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-sleek 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-sleek 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-sleek on npm has been identified as a malicious package (version 7.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019847

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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