Which versions of chai-as-gateway are malicious?

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

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

chai-as-gateway is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

chai-as-gatewaynpm

chai-as-gateway is a confirmed malicious npm package (MAL-2026-14200) that steals credentials and exfiltrates sensitive data (malicious version 7.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-gateway (npm)

MAL-2026-14200

Immediate action

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

npm uninstall chai-as-gateway

What this malware does

The package advertises itself as a logger (README and type definitions copied wholesale from pinojs/pino) but its exported middleware is a no-op that simply calls next(). index.js unconditionally executes require('./lib/config') at module top level, and lib/config.js is a ~4MB obfuscator.io-style blob (string-array rotate loader, ~24k entries, hex-escaped identifiers) whose only purpose is to run on import. The obfuscated blob contains references to child_process exec/spawn, axios (declared as a runtime dependency in package.json), fs directory traversal via withFileTypes, the path fragment.aws, and the full base64 alphabet — the standard shape of an installer-secret harvester that walks the home directory for AWS credentials and exfiltrates over HTTP. The package name resembles unrelated popular packages, the description string ('vulnerabilities management document') does not match the pino-cloned documentation, and author metadata is a generic [email protected] address. Requiring this package auto-executes attacker-controlled code on the installer.

Malicious versions

1 flagged

7.1.5

Indicators of compromise (SHA-256)

f90afdde9240783f1f869b875b7967490cf579e1bae0986861498f8c98c0d973

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-gateway (version 7.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-gateway across your stack and pipelines.
If you installed it — respond
chai-as-gateway is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If chai-as-gateway 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-gateway 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-gateway on npm has been identified as a malicious package (version 7.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018289

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database