Which versions of gpt-chat-cli are malicious?

The following npm versions of gpt-chat-cli are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate gpt-chat-cli if I installed it?

gpt-chat-cli 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 gpt-chat-cli — how do I know if it already compromised me?

If gpt-chat-cli 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 gpt-chat-cli part of a known attack campaign?

Yes — gpt-chat-cli is associated with the IN-MAL-2026-007424, IN-MAL-2026-007425 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 gpt-chat-cli 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 gpt-chat-cli (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gpt-chat-cli across your stack and pipelines.

Malicious package

gpt-chat-clinpm

Malicious code in gpt-chat-cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6375

Immediate action

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

npm uninstall gpt-chat-cli

What this malware does

collect.js bundles a host-reconnaissance and exfiltration payload. It loads child_process, fs, os, http, and https, reads os.hostname() and os.homedir(), enumerates filesystem paths via fs.existsSync(), and POSTs the collected data to the hardcoded endpoint http://aab.sportsontheweb.net (collect.js line 13, POST at line 366). The destination is unrelated to any documented purpose of a 'GPT chat CLI' package and matches the shape of a system-information stealer. Installing this package places attacker-controlled data-collection code into the install tree.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

8ccdee952af3407e4e33c563dcd8cab4fe48d6a9ddeea6e008b4dbda0f7ce578

e8890af695b137878736a36dae473487015eb1954c494fec0b5a6041f0817832

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 gpt-chat-cli (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gpt-chat-cli across your stack and pipelines.
If you installed it — respond
gpt-chat-cli 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 gpt-chat-cli 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 gpt-chat-cli 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. gpt-chat-cli on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007424IN-MAL-2026-007425

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gpt-chat-cli-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