Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

chai-lognpm

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

Malicious code in chai-log (npm)

MAL-2026-10426
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall chai-log

What this malware does

[email protected] presents itself as a Mocha reporter mirroring the legitimate eth-gas-reporter project (matching author name, README, and badges), but the exported reporter function reaches only a dropper branch. In index.js, a dead-code guard (var opt = 1; if (!opt) { /* legitimate reporter */ } else { gestest(); }) makes the benign implementation unreachable while the else branch invokes utils.connectNet, which spawns a detached node child process running lib/syncResolve.js. That subprocess fetches JavaScript from https://testlog.edgeone.cool/data.json and executes the response via new Function.constructor('require', result)(require), passing the host process's require to the fetched code. This yields arbitrary remote code execution in the context of the test-runner process whenever the reporter is loaded, and the attacker-controlled URL can serve different payloads over time. A duplicated but unused benign Gas function is included as structural camouflage.

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.0

Indicators of compromise (SHA-256)

f8ffc5e8b4e25d2d7787eb9f3bb9607114e5e4290f0afe2350499b78d5f95642
27dc63c0979b4150d7d64ae89958322fa744eb35f4c7373d9e20f30c7b70d768

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-log (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-log across your stack and pipelines.

  2. If you installed it — respond

    Remove chai-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.

  3. Did it already run?

    If chai-log 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.

  4. How O3 protects you

    O3 blocks chai-log 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-log on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009861GHSA-2534-xr99-f4wh

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

chai-log (npm) malicious package — MAL-2026-10426 | O3 Security