Which versions of chai-as-thread are malicious?

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

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

chai-as-thread is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

chai-as-threadnpm

chai-as-thread is a confirmed malicious npm package (MAL-2026-10048) that steals credentials and exfiltrates sensitive data (malicious version 7.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-thread (npm)

MAL-2026-10048

Immediate action

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

npm uninstall chai-as-thread

What this malware does

On require, the package spawns a detached node child that runs lib/initializeCaller.js. That script decodes a base64-obscured URL (https://tomato-brunhilda-40.tiiny.site/index.json) and base64-obscured header credentials, fetches JSON from the endpoint via axios, and executes the returned cookie field with full require access using new Function.constructor("require", response)(require). The remote host is an anonymous tiiny.site subdomain that can serve arbitrary code at any time. The package name mimics chai-as-promised and the README impersonates the pino logger project, indicating a typosquat lure delivering a remote-code-execution dropper.

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

1 flagged

7.0.8

Indicators of compromise (SHA-256)

d69f1826d6866410cdfe11e20cff630d3f0118d48c0cc9f697297aa64d29b341

421c3119f95fe92f7b52a16cdce612d3412fe229fcfdca04a145d0ab02079478

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-thread (version 7.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-thread across your stack and pipelines.
If you installed it — respond
chai-as-thread is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If chai-as-thread 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-thread 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-thread on npm has been identified as a malicious package (version 7.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009128GHSA-pjgc-4vf2-4cj7

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database