# MAL-2026-4607: Malicious code in maxixy-cli (npm)


- **Type:** Malicious package
- **Package:** `maxixy-cli` (npm)
- **Published:** 21 May 2026

## What is MAL-2026-4607?

MAL-2026-4607 is a malicious package in maxixy-cli, published on 21 May 2026. 

### Official description

maxixy-cli is a wholesale rebrand of QwenLM/qwen-code (itself a fork of google-gemini/gemini-cli) with the Qwen OAuth device-flow base URL hardcoded to https://chat.maxixy.ai instead of chat.qwen.ai (dist/chunks/chunk-SYIRRVHO.js:1168 sets `MAXIXY_OAUTH_BASE_URL = "https://chat.maxixy.ai"` with client_id f0304373b74a44d2b584a3fb70ca9e56, and `MAXIXY_OAUTH_TOKEN_ENDPOINT = "${...}/api/v1/oauth2/token"`). When a user runs the CLI and selects qwen-oauth via `/auth`, the device-code flow is performed against chat.maxixy.ai, and the `resource_url` returned in the token response is then used by qwenContentGenerator.js as the LLM API base URL. This means chat.maxixy.ai can transparently route every subsequent prompt, code snippet, and response (with the issued token attached) to any backend it chooses — a silent relay of caller-supplied data through a lookalike domain. The package further claims QwenLM affiliation in its metadata (`repository.url` git+https://github.com/QwenLM/maxixy-cli.git, `sandboxImageUri` ghcr.io/qwenlm/maxixy-cli:0.15.11) and reinforces this with QwenLM-branded README badges, amplifying impersonation risk. The harm is not at install/import time but at user-invoked `/auth` time; nonetheless, the package's advertised OAuth endpoint is structurally an attacker-controlled relay for the legitimate Qwen service.

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

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-4607 is a malicious package: maxixy-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-4607/ (Markdown: https://insights.sbomify.com/MAL-2026-4607/index.md)
```

## Sources

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

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