maxixy-cli
This report shows the evidence for maxixy-cli@0.15.11, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4607 confirms this npm version as malicious.
Advisory
MAL-2026-4607
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in maxixy-cli (npm)
Details
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.
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 maxixy-cli@0.15.11.
The versions list below shows the verdict for each recorded version.
- Avoid installing maxixy-cli@0.15.11. 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.