@xhscopy-ai/cli@0.0.157
Configure Claude Code, Codex, Grok Build and other coding tools for Xhscopy AI with one command
AI Security Review
scanned 1d ago · by lpm-firewall-aiThis is not clear malware: the collected fields are usage and platform telemetry, and no credential theft or unrelated collection was identified. However, runtime telemetry is enabled by default and was not disclosed in the reviewed package material, so it warrants a warning.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI, except version/help paths that skip telemetry; users can disable telemetry with TELEMETRY=0, false, or off.
Impact
The service receives usage events and an install identifier without a clear disclosure in the reviewed package description.
Mechanism
The CLI queues command events and platform/runtime identifiers, then posts them to /api/platform/vibecode/telemetry through its configured service base URL.
AI rationale
This is not clear malware: the collected fields are usage and platform telemetry, and no credential theft or unrelated collection was identified. However, runtime telemetry is enabled by default and was not disclosed in the reviewed package material, so it warrants a warning.
Evidence
dist/lib/telemetry.jsdist/lib/command.js
Network endpoints1
configured service base URL + /api/platform/vibecode/telemetry
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- CLI telemetry is enabled by default; it can be disabled with TELEMETRY=0, false, or off.
- Telemetry sends install ID, CLI version, brand, OS, OS release, architecture, Node version, and command events to the telemetry endpoint.
- Normal CLI execution records the command and selected flag arguments, then flushes telemetry.
Evidence against
- The package is a CLI for configuring coding tools, and the reviewed process and install commands serve that purpose.
- package.json declares no lifecycle scripts.
- Telemetry does not visibly collect credentials or file contents in the reviewed event fields.
Behavioral surface
ChildProcessEnvironmentVarsNetworkShell
HighEntropyStringsMinifiedUrlStrings
NoLicense
Source & flagged code
7 flaggeddist/lib/tools/chatgpt-desktop.jsView file
1import{spawnSync as t}from"child_process";import{logger as n}from"../../utils/logger.js";import{brand as e}from"../brand.js";import{powerShellEnv as r}from"../powershell-env.js";im...
High
Child Process
Package source references child process execution.
dist/lib/tools/chatgpt-desktop.jsView on unpkg · L1dist/lib/tools/tool-installs.jsView file
1import{spawnSync as t}from"child_process";import{existsSync as n,realpathSync as r,statSync as e}from"fs";import{delimiter as o,dirname as s,isAbsolute as i,join as a}from"path";im...
High
1import{spawnSync as t}from"child_process";import{existsSync as n,realpathSync as r,statSync as e}from"fs";import{delimiter as o,dirname as s,isAbsolute as i,join as a}from"path";im...
Findings
1 Critical5 High4 Medium3 Low
CriticalPrevious Version Dangerous Deltadist/lib/tools/desktop-app-installer.js
HighChild Processdist/lib/tools/chatgpt-desktop.js
HighShelldist/lib/tools/tool-installs.js
HighSame File Env Network Executiondist/lib/tools/claude-desktop-cli.js
HighTrigger Reachable Persistencedist/lib/env-cleanup.js
HighRuntime Package Installdist/lib/tools/tool-installs.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/lib/persistent-env.js
MediumStructural Risk Force Deep Review
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @xhscopy-ai/cli@0.0.157.
See all versions of @xhscopy-ai/cli for other recorded verdicts.
- Review the evidence and your use of @xhscopy-ai/cli@0.0.157 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.