Which versions of chai-as-mock are malicious?

The following npm versions of chai-as-mock are flagged malicious: 7.2.5, 7.2.6. Treat any of these as compromised.

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

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

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

Yes — chai-as-mock is associated with the GHSA-vp25-hhqc-cx25, RLMA-2026-01151, RLUA-2026-01721 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-mock across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chai-as-mock (2 malicious versions).

Malicious package

chai-as-mocknpm

Advisory published Mar 3, 2026Updated Apr 1, 2026

chai-as-mock is a confirmed malicious npm package (MAL-2026-1191) that executes malicious code on install (malicious versions 7.2.5, 7.2.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-mock (npm)

MAL-2026-1191

Immediate action

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

npm uninstall chai-as-mock

What this malware does

The package chai-as-mock was found to contain malicious code.

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

2 flagged

7.2.57.2.6

Indicators of compromise (SHA-256)

6ab0e6eb41241ac06a623d9e7fa230c2d68067904fd48aa422ab8c2db1cd23e4

303ff6a2f2561ea67c1d084cbfc1ebdd5364668aab3d06257cb2cbeea42ce5a3

c1df9f77c38ae017a6e1f01ce7be952cc73f6ba4e00f8cc2f6cbfdf456964c22

a7f1769422fdc2532d7b1168da4ec048335b772402b1b00f7bbe4bb71063bdbb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chai-as-mock (2 malicious versions).
If you installed it — respond
Remove chai-as-mock 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-mock 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-mock on npm has been identified as a malicious package (versions 7.2.5, 7.2.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vp25-hhqc-cx25RLMA-2026-01151RLUA-2026-01721

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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