Which versions of chai-as-launched are malicious?

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

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

Remove chai-as-launched from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — chai-as-launched is associated with the RLMA-2026-04990, RLUA-2026-06118 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-launched across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chai-as-launched (version 3.51.1).

Malicious package

chai-as-launchednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

chai-as-launched is a confirmed malicious npm package (MAL-2026-7235) that executes malicious code on install (malicious version 3.51.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-launched (npm)

MAL-2026-7235

Immediate action

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

npm uninstall chai-as-launched

Malicious versions

1 flagged

3.51.1

Indicators of compromise (SHA-256)

8e1e9fb8ac0c4bd87d1bd89d4487580d568ada092b66e9d7f07e8f8b10fcf9dd

78479742f8321a44f10539bec6b5da507149af6e7f4aa710aa6b2afe59ea8333

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chai-as-launched (version 3.51.1).
If you installed it — respond
Remove chai-as-launched from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If chai-as-launched 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-launched on npm has been identified as a malicious package (version 3.51.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04990RLUA-2026-06118

References

Credits

ReversingLabs · finder

Detect & block this

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