Which versions of chain-as-log are malicious?

The following npm versions of chain-as-log are flagged malicious: 3.0.1. Treat any of these as compromised.

How do I remediate chain-as-log if I installed it?

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

If chain-as-log was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is chain-as-log part of a known attack campaign?

Yes — chain-as-log is associated with the IN-MAL-2026-010626 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 chain-as-log across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chain-as-log (version 3.0.1).

Malicious package

chain-as-lognpm

Advisory published Jul 15, 2026Updated Jul 15, 2026

chain-as-log is a confirmed malicious npm package (MAL-2026-10668) that executes malicious code on install (malicious version 3.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chain-as-log (npm)

MAL-2026-10668

Immediate action

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

npm uninstall chain-as-log

What this malware does

chain-as-log advertises itself as a chai plugin providing deep-equal-excluding assertion helpers. At plugin load time (when a consumer calls chai.use(chainLog)), the main module invokes a resetor() function that attempts to require an unrelated package 'dbconnectify' and, on failure, silently shells out to npm to install it with { 'no-save': true, loglevel: 'silent' }, then instantiates it and calls queryDBConnect(). The resetor() call is placed between two legitimate Assertion.addMethod registrations, and the catch block swallows all failure output. This behavior is unrelated to the package's advertised chai purpose and constitutes a stager: loading chain-as-log fetches attacker-controlled code from an unrelated npm package and executes it on the installer's host.

Malicious versions

1 flagged

3.0.1

Indicators of compromise (SHA-256)

86f8946bf37a9861239e59a78f2d003612494061d5aa60c5f7e54379e72f0ac7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chain-as-log (version 3.0.1).
If you installed it — respond
Remove chain-as-log 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 chain-as-log was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. chain-as-log on npm has been identified as a malicious package (version 3.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010626

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chain-as-log-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