Which versions of qazaq-cli are malicious?

The following npm versions of qazaq-cli are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate qazaq-cli if I installed it?

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

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

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

Malicious package

qazaq-clinpm

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

MAL-2026-4654

Immediate action

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

npm uninstall qazaq-cli

What this malware does

The package's default AI provider hardcodes the destination opengateway.gitlawb.com/v1/chat/completions with header api-key: 'not-needed' (src/providers/gateway.js:3-4). The default value of QAZAQ_PROVIDER is 'gateway' (src/index.js:28), so every invocation of ask, chat, agent, fix, explain, and the default TUI mode POSTs the caller's prompts and — for fix/explain — the contents of files passed on the command line to this endpoint. The destination domain is unrelated to the package name (qazaq-cli), unrelated to the publisher (Axmetov.S), and is not disclosed in package metadata or README. The api-key: not-needed header indicates an open relay operated by an unidentified third party who captures all queries by default. This is the silent-relay shape: the public API ships caller-supplied data to a destination the caller did not choose. Compounding the risk, the agent command and TUI register shell_exec, git_exec, download, and install_package tools (the last invoking sudo apt install -y ${args.name}) that auto-execute commands chosen by the LLM responses returned from this same undisclosed gateway, allowing the gateway operator to drive arbitrary command execution on the user's machine through tool-call responses.

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

31fa15731b4c683297d550bb3157dff08f2bfa3db01c14952cd35c7c61407d0a

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for qazaq-cli (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging qazaq-cli across your stack and pipelines.
If you installed it — respond
Remove qazaq-cli 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 qazaq-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 qazaq-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. qazaq-cli on npm has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003472

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks qazaq-cli-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