Which versions of chai-as-align are malicious?

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

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

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

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

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

Malicious package

chai-as-alignnpm

Malicious code in chai-as-align (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10039

Immediate action

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

npm uninstall chai-as-align

What this malware does

The package presents itself as a testing/logging helper but its exported middleware factory spawns a detached background Node child that runs lib/initializeCaller.js. That script base64-decodes a hidden URL (https://amethyst-lorrin-26.tiiny.site/index.json) from a fake process.env stub, fetches its 'cookie' field over HTTPS with an 'x-secret-key' header, and executes the returned body via new Function.constructor('require', response) bound to the real require, in a retry loop. This yields full remote code execution on the installer's machine whenever the exported middleware is invoked. The destination is an anonymous file-hosting service (tiiny.site) whose contents are attacker-mutable. The package name closely resembles the popular chai-as-promised library, and its declared description/keywords do not match the shipped code, indicating typosquat delivery of the dropper. The detached+unref'd child with stdio ignored is used to hide the payload's activity from the consuming application.

Malicious versions

1 flagged

7.1.0

Indicators of compromise (SHA-256)

791f5dcd4f623d5301bc3abf922c5f0e4ff716017fe67d3673c778e9d31b0776

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

Campaign

IN-MAL-2026-009136

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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