Which versions of chai-prop are malicious?

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

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

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

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

Yes — chai-prop is associated with the GHSA-4p6w-3gcj-crr5, RLMA-2026-01188 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-prop 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-prop (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-prop across your stack and pipelines.

Malicious package

chai-propnpm

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

MAL-2026-856

Immediate action

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

npm uninstall chai-prop

What this malware does

The package chai-prop 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)

46a6572ddbd6c8ceef059f6e07126d160a849cf4912b1befe7b4523393c72484

6708dacd87e4aafa4ffafa5b20fff5ae416d6580ba01ddcaaa51ca08f0317c85

e199a13b0204ab4a5883a8e1ba698e9b951ca030d7bf803ba772f47a0d100207

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-prop (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-prop across your stack and pipelines.
If you installed it — respond
Remove chai-prop 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-prop 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-prop 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-prop 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-4p6w-3gcj-crr5RLMA-2026-01188

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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