qwenproxy-cli@1.2.8
High-performance OpenAI & Anthropic compatible API gateway for Qwen with multi-account rotation, interactive TUI, and resilient tool calling.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe source shows explicit-user AI-agent configuration mutation, including optional active-provider selection, which is warning-worthy under the agent policy. It does not show an install hook, a package-controlled remote recipient, or a confirmed active attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs qpx sync or the sync script.
Impact
A user-requested configuration change can redirect future client requests to the configured local gateway; no confirmed covert exfiltration was established.
Mechanism
The command adds a QwenProxy provider and can select it as the active model provider.
AI rationale
The source shows explicit-user AI-agent configuration mutation, including optional active-provider selection, which is warning-worthy under the agent policy. It does not show an install hook, a package-controlled remote recipient, or a confirmed active attack.
Evidence
bin/qwenproxy.jssrc/sync/index.tssrc/sync/codex.ts~/.codex/config.toml
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package exposes sync as a user-invoked script and has no install lifecycle hook.
- The qpx launcher routes only the explicit sync command to the client synchronization program.
- Synchronization selects external client configuration paths, including Codex, and defaults its gateway host to localhost.
- The Codex synchronizer creates a QwenProxy provider block containing a configured API key and gateway URL.
- The updater checks the npm registry only when its update routine is invoked.
Evidence against
- No automatic install-time configuration mutation was found.
- The reviewed synchronization gateway defaults to a local host rather than a package-controlled remote endpoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedbin/update.jsView file
7L8: import { spawnSync } from "node:child_process";
L9: import fs from "node:fs";
High
91encoding: "utf-8",
L92: shell: true,
L93: timeout: 30000,
High
src/core/accounts.tsView file
22function parseEnvAccounts(): QwenAccount[] {
L23: const envAccounts = process.env.QWEN_ACCOUNTS;
L24: if (!envAccounts) return [];
Low
Weak Crypto
Package source references weak cryptographic algorithms.
src/core/accounts.tsView on unpkg · L22Findings
5 High3 Medium5 Low
HighChild Processbin/update.js
HighShellbin/update.js
HighSame File Env Network Executionbin/qwenproxy.js
HighSandbox Evasion Gated Capabilitybin/qwenproxy.js
HighPrevious Version Dangerous Deltabin/qwenproxy.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptosrc/core/accounts.ts
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to qwenproxy-cli@1.2.8.
See all versions of qwenproxy-cli for other recorded verdicts.
- Review the evidence and your use of qwenproxy-cli@1.2.8 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.