Which versions of chai-as-forgeted are malicious?

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

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

chai-as-forgeted 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-forgeted — how do I know if it already compromised me?

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

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

Malicious package

chai-as-forgetednpm

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

Malicious code in chai-as-forgeted (npm)

MAL-2026-6219

Immediate action

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

npm uninstall chai-as-forgeted

What this malware does

Package name impersonates the popular chai-as-promised assertion library, but its package.json description and keywords are copied from pino and the code is unrelated to chai. The package's main entry exports a middleware factory that spawns lib/caller.js as a detached node child process. lib/caller.js base64-decodes a hardcoded URL pointing at api.jsonstorage.net (a mutable third-party JSON storage service), GETs the JSON document, extracts the cookie field, and executes its contents via new Function.constructor('require', s)(require) with full access to require. The C2 URL and request headers are stored as base64 strings inside a locally redefined process object that shadows the real process global, then decoded with atob at runtime. Any consumer who installs and invokes the exported middleware triggers arbitrary attacker-controlled code execution; the attacker can rotate the payload served by the JSON storage endpoint at will.

Malicious versions

1 flagged

9.24.6

Indicators of compromise (SHA-256)

b6b32b714919c755532ed3d2695d1966568c24878e9721a5d756896d81881020

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-forgeted (version 9.24.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-forgeted across your stack and pipelines.
If you installed it — respond
chai-as-forgeted 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-forgeted 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-forgeted 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-forgeted on npm has been identified as a malicious package (version 9.24.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007065

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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