Which versions of chai-as-flex are malicious?

The following npm versions of chai-as-flex are flagged malicious: 0.0.1-security, 7.2.8. Treat any of these as compromised.

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

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

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

Yes — chai-as-flex is associated with the GHSA-p3rj-3q6f-wvp8, RLMA-2026-01720, RLUA-2026-01914 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-flex 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-flex (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-flex across your stack and pipelines.

Malicious package

chai-as-flexnpm

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

MAL-2026-1343

Immediate action

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

npm uninstall chai-as-flex

What this malware does

The package chai-as-flex 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

0.0.1-security7.2.8

Indicators of compromise (SHA-256)

43ec01f2ce6223022a2f8808fefb3586a644577acb62fbe4184add705f616914

e209e357d41cfd5d03c91f7b03e155685a36191ac79740818656d310c71390fe

7d3dd122457178506b70e954838c25e2dcdfde7c2f918472a6acaaec11c858c8

39f0d768abbc0ae21f3c923dd058a2db1d84fe97360ddfd9cbbdf39960c84876

Detection & response playbook

Malicious package

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

Campaign

GHSA-p3rj-3q6f-wvp8RLMA-2026-01720RLUA-2026-01914

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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