xchange-cli@0.12.24
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe automatic ads module receives account-related token values and uses them in authenticated requests, while obfuscation conceals the destination and prevents confirming the flow's purpose. This is a real but unproven telemetry risk, so the package warrants a warning rather than a block.
Decision evidence
public snapshot- The desktop bundle automatically starts an ads module and supplies callbacks for a token, an own token, a service URL, and a session token.
- The obfuscated ads module sends requests with a Bearer authorization header to an encoded API origin; its default preset is also encoded.
- The ads module can request a house credential from the configured service URL using an authorization token.
- The executable bundles are heavily obfuscated, so the ads destination and the full purpose of the token flows cannot be verified from readable source.
- The manifest has no lifecycle scripts; the published bin imports the CLI entry point.
- The package describes itself as a model router and AI coding tool, which accounts for ordinary network and process use.
- The ads credential request uses the app-provided service URL rather than a readable hard-coded foreign host.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/cli/src/systemd.jsView on unpkg · L1Package source references dynamic require/import behavior.
bin/xchange.jsView on unpkg · L11Findings
Affected versions and remediation
This report applies to xchange-cli@0.12.24.
See all versions of xchange-cli for other recorded verdicts.
- Review the evidence and your use of xchange-cli@0.12.24 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.