Which versions of maxixy-cli are malicious?

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

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

maxixy-cli is a typosquat — you almost certainly intended a legitimately-named package. Remove maxixy-cli, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed maxixy-cli — how do I know if it already compromised me?

If maxixy-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is maxixy-cli part of a known attack campaign?

Yes — maxixy-cli is associated with the IN-MAL-2026-003989 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 maxixy-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for maxixy-cli (version 0.15.11).

Malicious package

maxixy-clinpm

Advisory published May 21, 2026Updated May 26, 2026

maxixy-cli is a confirmed malicious npm package (MAL-2026-4607) that typosquats a legitimate package to trick installs (malicious version 0.15.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in maxixy-cli (npm)

MAL-2026-4607

Immediate action

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

npm uninstall maxixy-cli

What this malware does

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.

Malicious versions

1 flagged

0.15.11

Indicators of compromise (SHA-256)

1b8df03da54eaa00b887a27395e7b7c42b02a982b1e9df9d82a5b0c243d0ba95

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for maxixy-cli (version 0.15.11).
If you installed it — respond
maxixy-cli is a typosquat — you almost certainly intended a legitimately-named package. Remove maxixy-cli, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If maxixy-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. maxixy-cli on npm has been identified as a malicious package (version 0.15.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003989

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks maxixy-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

Explore

All malware advisories How O3 detects malware Vulnerability database