# chai-as-streamed (npm) malicious package — MAL-2026-3657 | O3 Security

Malicious package

# chai-as-streamednpm

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

Malicious code in chai-as-streamed (npm)

MAL-2026-3657

Immediate action

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

npm uninstall chai-as-streamed

## What this malware does

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

2.0.11

## Indicators of compromise (SHA-256)

fef1582aa7fb15599bd48e6f077be4d1a577d3916cf2c2650893f0406ede8ea3

21151df3afb06fe816f0067e571a7eb19bc7581fce6570adf894df423af302ea

## Detection & response playbook

Malicious package

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

## Campaign

GHSA-r2pr-8h52-3v7xRLMA-2026-04999

## References

-   [github.com](https://github.com/advisories/GHSA-r2pr-8h52-3v7x)

## Credits

-   ReversingLabs · finder

## Detect & block this

O3 blocks chai-as-streamed\-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](/malware-detection) [Runtime egress monitoring](/egress-monitor)

## Explore

[All malware advisories](/malware) [How O3 detects malware](/malware-database) [Vulnerability database](/vulnerability)