Which versions of chai-as-mno are malicious?

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

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

chai-as-mno is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-as-mno, 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-mno — how do I know if it already compromised me?

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

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

Malicious package

chai-as-mnonpm

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

Malicious code in chai-as-mno (npm)

MAL-2026-14427

Immediate action

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

npm uninstall chai-as-mno

What this malware does

The package name mimics chai-as-promised and its README, badges, and license text are copied from an unrelated project (pino), while the package.json description is unrelated boilerplate. The declared main index.js exports a trivial no-op Express middleware (_req,_res,next)=>next() and unconditionally executes require('./lib/config') at import time. lib/config.js is a ~4MB single-line file heavily obfuscated with an obfuscator.io string-array scheme (string array d of length 23971 with rotation, hex-named identifiers, nested decoder functions j/T, control-flow flattening, and ~40,000 inline-decoded strings). The visible surface API provides no legitimate reason to ship a multi-megabyte opaque blob as a config module, and merely requiring the package runs that payload in the installer's Node process. The combination of impersonation cover story, mismatched README/description, no-op public API, and an obfuscator.io-grade payload executed on require is the loader/dropper shape.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

2e94e194f078c230d6c6b15efcddc54b133fd52c890a55b0f8bdb4c680452381

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

Campaign

IN-MAL-2026-018654

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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