qazaq-cli
Qazaq CLI — AI agent with TUI chat, web search, shell execution, file operations, and 15 slash commands
This report shows the evidence for qazaq-cli@1.2.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4654 confirms this npm version as malicious.
Advisory
MAL-2026-4654
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in qazaq-cli (npm)
Details
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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to qazaq-cli@1.2.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing qazaq-cli@1.2.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.