Which versions of chai-as-synced are malicious?

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

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

chai-as-synced is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-as-synced, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — chai-as-synced is associated with the IN-MAL-2026-007582 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-synced 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-synced (version 6.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-synced across your stack and pipelines.

Malicious package

chai-as-syncednpm

chai-as-synced is a confirmed malicious npm package (MAL-2026-6497) that typosquats a legitimate package to trick installs (malicious version 6.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-synced (npm)

MAL-2026-6497

Immediate action

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

npm uninstall chai-as-synced

What this malware does

Package name 'chai-as-synced' impersonates the well-known 'chai-as-promised'. On require, index.js spawns a detached, stdio-ignored Node child running lib/initializeCaller.js. That script decodes a base64-obfuscated URL (https://amethyst-lorrin-26.tiiny.site/index.json) and an 'x-secret-key' header literal stored inside a fake local process.env object, performs an HTTPS GET to that anonymous static-hosting endpoint, and passes the returned 'cookie' field to new Function.constructor(...) invoked with require injected, retried up to 5 times. The fetched JavaScript runs in the installer's Node process with full require access. The destination obfuscation, detached/unref'd child, and hidden stdio together indicate a covert loader; the declared dependencies (sqlite3, request, axios) and package keywords do not match the advertised purpose.

Malicious versions

1 flagged

6.0.3

Indicators of compromise (SHA-256)

7bc0ee3e6a8341e046b84880f9faf0a4750f4a261a791b95d1267066d7828071

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-synced (version 6.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-synced across your stack and pipelines.
If you installed it — respond
chai-as-synced is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-as-synced, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If chai-as-synced 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-synced 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-synced on npm has been identified as a malicious package (version 6.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007582

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database