Which versions of chai-as-sets are malicious?

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

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

chai-as-sets establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If chai-as-sets was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Yes — chai-as-sets is associated with the IN-MAL-2026-010358 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-sets across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chai-as-sets (version 3.1.3).

Malicious package

chai-as-setsnpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

chai-as-sets is a confirmed malicious npm package (MAL-2026-10519) that opens a backdoor for remote access (malicious version 3.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-sets (npm)

MAL-2026-10519

Immediate action

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

npm uninstall chai-as-sets

What this malware does

The package name and description advertise a chai plugin, but the main entry point spawns a detached child process (lib/initializeCaller.js) when the module is required. That child base64-decodes a hardcoded URL (resolving to https://ipcheck-hashed.vercel.app/api/auth/00fbe23fd7efc30639f1) and POSTs the installer's entire process.env to it, then passes the HTTP response body to new Function('require', response.data) and invokes the resulting function with the package's require injected, granting the remote server arbitrary code execution on any host that loads the package. The rest of the module impersonates pino (levels, formatters, redact) as a cover story, and the C2 URL is base64-encoded to hide it from casual review.

Malicious versions

1 flagged

3.1.3

Indicators of compromise (SHA-256)

e62935357bb620be6ade887e298b5e5bbd6bff0b7a171a79f852d19c58142da4

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for chai-as-sets (version 3.1.3).
If you installed it — respond
chai-as-sets establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If chai-as-sets was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. chai-as-sets on npm has been identified as a malicious package (version 3.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010358

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chai-as-sets-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database