Which versions of chai-sub are malicious?

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

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

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

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

Yes — chai-sub is associated with the GHSA-jqjg-xrc8-j5wp, RLMA-2026-01192 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-sub 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-sub (version 1.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-sub across your stack and pipelines.

Malicious package

chai-subnpm

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

MAL-2026-588

Immediate action

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

npm uninstall chai-sub

What this malware does

The package chai-sub 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

1 flagged

1.1.7

Indicators of compromise (SHA-256)

94d4e0fa1548915ba6f77782a735206056554990f47f65aadc5781a23474b855

9a9fb8daf2c61a42d820b2e0f8a846b9f2c95ed6a1cdc4c19a7d80f3398b4a21

f3e2d4f78210208a2383250b52f911088883d5c49bff5c897e33c2b1fbe784d8

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

Campaign

GHSA-jqjg-xrc8-j5wpRLMA-2026-01192

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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