Which versions of chai-as-elevated are malicious?

Every published version of chai-as-elevated on npm is considered malicious. Remove the package entirely.

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

chai-as-elevated establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed chai-as-elevated — how do I know if it already compromised me?

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

Yes — chai-as-elevated is associated with the GHSA-p5jq-3963-9qmx 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-elevated 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-elevated (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-elevated across your stack and pipelines.

Malicious package

chai-as-elevatednpm

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

MAL-2026-2887

Immediate action

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

npm uninstall chai-as-elevated

What this malware does

chai-as-elevated is a malicious npm package that when imported downloads a C2 dropper from https://api.npoint[.]io/545d3d0c167b8dde920f and executes it (similar to malware in to chai-await-test).

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

c1611aa9c56a1974bb7f7ee0f19270a5dc8881eb857e94c0f1fd151eefbe45ae

b210d1bc8bdcb7039a0525c6c37e93c5ed2d5d0c3a5ad8e044d6a286bdc10930

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-elevated (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-elevated across your stack and pipelines.
If you installed it — respond
chai-as-elevated establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If chai-as-elevated 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-elevated 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-elevated on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p5jq-3963-9qmx

References

Credits

Amazon Inspector · finder
indece · finder

Detect & block this

O3 blocks chai-as-elevated-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring