xchange-cli@0.12.23
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe desktop app sends ad engagement telemetry by default and provides an opt-out, but the inspected README does not disclose this activity. The visible reports contain ad receipt fields, so the evidence supports a warning for undisclosed telemetry rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.
Trigger
Electron app startup, unless XCHANGE_ADS=0 is set.
Impact
The ad service can associate sponsored-card engagement with the supplied account token. The inspected flow does not establish theft of unrelated service credentials or user content.
Mechanism
The app reads account configuration, supplies an authorization token to the ad subsystem, requests creatives, and reports ad receipts.
AI rationale
The desktop app sends ad engagement telemetry by default and provides an opt-out, but the inspected README does not disclose this activity. The visible reports contain ad receipt fields, so the evidence supports a warning for undisclosed telemetry rather than a malicious verdict.
Evidence
dist/app/dist/main.jsdist/app/dist/ads.js
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The Electron app starts sponsored-card handling on readiness by default; only XCHANGE_ADS=0 disables it.
- The app reads its account configuration and provides account tokens to the ad subsystem, including a token fetched from the configured service URL.
- Ad requests send an authorization header and report creative ID, display time, dwell time, theme, and outcome.
Evidence against
- The reported fields describe ad delivery and engagement; the inspected request does not show prompts, code, or tool output being sent.
- The optional house credential is fetched from the user-configured service URL using that service's session token.
- The package manifest has no install, preinstall, or postinstall lifecycle script.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStrings
Source & flagged code
6 flaggeddist/cli/src/systemd.jsView file
1const u=d,v=d,w=d;(function(h,i){const n=d,o=d,p=d,j=h();while(!![]){try{const k=-parseInt(n(0xd0))/(-0x25d8+-0xfd8+0x35b1)*(-parseInt(n(0x13e))/(0x1*-0xfea+-0x22fc+0x32e8))+parseI...
High
Child Process
Package source references child process execution.
dist/cli/src/systemd.jsView on unpkg · L1bin/xchange.jsView file
11const entry = fs.existsSync(built) ? built : path.join(root, "packages", "cli", "src", "index.ts");
L12: await import(pathToFileURL(entry).href);
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/xchange.jsView on unpkg · L11dist/app/dist/main.jsView file
1
Findings
6 High4 Medium5 Low
HighChild Processdist/cli/src/systemd.js
HighShell
HighSame File Env Network Executiondist/app/dist/main.js
HighObfuscated Payload Loaderdist/ui/presets-fallback.js
HighCross File Remote Execution Contextdist/cli/src/index.js
HighSemantic Analysis Limiteddist/app/dist/ads.js#virtual:normalized:round1
MediumDynamic Requirebin/xchange.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowCopyleft License
Affected versions and remediation
This report applies to xchange-cli@0.12.23.
See all versions of xchange-cli for other recorded verdicts.
- Review the evidence and your use of xchange-cli@0.12.23 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.