Which versions of chai-fetchs are malicious?

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

How do I remediate chai-fetchs if I installed it?

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

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

Yes — chai-fetchs is associated with the RLMA-2026-05009, RLUA-2026-06138 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-fetchs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chai-fetchs (version 3.1.9).

Malicious package

chai-fetchsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in chai-fetchs (npm)

MAL-2026-7244

Immediate action

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

npm uninstall chai-fetchs

Malicious versions

1 flagged

3.1.9

Indicators of compromise (SHA-256)

0bd26e08c5d6b4737053693da196dd2a9de0c03fed3f6c0940db27daa6abe015

1fc598579f3c16ae4c7e080cddba9473ef8ff9f8e16699ed954100deb33206ce

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05009RLUA-2026-06138

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks chai-fetchs-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