qwenproxy-cli@1.0.28
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 package has an explicit command that can reconfigure external AI clients, so it warrants a capability warning. Static inspection found no automatic lifecycle trigger or confirmed malicious payload.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs the qpx sync command.
Impact
Later client requests may use the local gateway rather than the previously selected provider.
Mechanism
The command routes selected client configurations to the local QwenProxy provider and writes its configured API key.
AI rationale
The package has an explicit command that can reconfigure external AI clients, so it warrants a capability warning. Static inspection found no automatic lifecycle trigger or confirmed malicious payload.
Evidence
~/.codex/config.toml~/.claude/settings.json~/.config/opencode/opencode.jsonc~/.omp/agent/models.yml
Network endpoints1
127.0.0.1:7936/v1
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The CLI dispatches synchronization only when the user supplies the sync command.
- The synchronization command invokes client configuration updates.
- The updater writes a QwenProxy provider and bearer token into the Codex configuration.
- No npm preinstall, install, or postinstall hook was found in package.json.
Evidence against
- The configuration mutation is an explicit user-command feature, not automatic installation behavior.
- The configured gateway defaults to a local loopback address.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedbin/qwenproxy.jsView file
17L18: import { spawn, spawnSync } from "node:child_process";
L19: import path from "node:path";
High
150const cmd = process.platform === "win32" ? "npx.cmd" : "npx";
L151: return spawnSync(cmd, ["--yes", "patchright", "install", "chromium"], {
L152: stdio: "inherit",
...
L156:
L157: let chosenHost = process.env.PLAYWRIGHT_DOWNLOAD_HOST;
L158: if (!chosenHost) {
...
L162: try {
L163: const probe = await fetch("https://cdn.playwright.dev", { method: "HEAD", signal: controller.signal });
L164: clearTimeout(probeTimer);
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
bin/qwenproxy.jsView on unpkg · L15015*/
L16: process.env.DOTENV_CONFIG_QUIET = "true";
L17:
L18: import { spawn, spawnSync } from "node:child_process";
L19: import path from "node:path";
...
L24: const require = createRequire(import.meta.url);
L25: const __dirname = path.dirname(fileURLToPath(import.meta.url));
L26: const packageRoot = path.resolve(__dirname, "..");
L27: const packageJsonPath = path.join(packageRoot, "package.json");
L28:
...
L34: try {
L35: const pkg = JSON.parse(fs.readFileSync(packageJsonPath, "utf-8"));
Findings
5 High3 Medium5 Low
HighChild Processbin/qwenproxy.js
HighShellsrc/tui/theme.ts
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.0.28.
See all versions of qwenproxy-cli for other recorded verdicts.
- Review the evidence and your use of qwenproxy-cli@1.0.28 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.