# MAL-2026-4654: Malicious code in qazaq-cli (npm)


- **Type:** Malicious package
- **Package:** `qazaq-cli` (npm)
- **Published:** 20 May 2026

## What is MAL-2026-4654?

MAL-2026-4654 is a malicious package in qazaq-cli, published on 20 May 2026. 

### Official description

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.

## What should I do about MAL-2026-4654?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4654 is a malicious package: qazaq-cli (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-4654/ (Markdown: https://insights.sbomify.com/MAL-2026-4654/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4654

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-4654/
Summaries are generated and may contain mistakes; the official description above is the record.