@tsuga/cli@1.138.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 14h ago · by lpm-firewall-aiThe CLI’s opt-in telemetry sends raw command-line arguments, including option values, to Tsuga’s API. Since those values can contain secrets or identifying details and the consent prompt only describes usage data, this is a telemetry risk that warrants a warning.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
A successful CLI run after telemetry consent is saved or granted in the interactive prompt, or a run with TSUGA_TELEMETRY=1/true.
Impact
Option values containing secrets or identifying details could be disclosed to Tsuga under a broad usage-data consent prompt.
Mechanism
The CLI adds the parsed command and up to 32 raw arguments beginning with the first flag to a usage payload, then posts it to the Tsuga API.
AI rationale
The CLI’s opt-in telemetry sends raw command-line arguments, including option values, to Tsuga’s API. Since those values can contain secrets or identifying details and the consent prompt only describes usage data, this is a telemetry risk that warrants a warning.
Evidence
dist/cli.js~/.config/tsuga/config.json
Network endpoints2
api.tsuga.com/v1/cli-runsapi.tsuga-staging.com/v1/cli-runs
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Opt-in run telemetry includes the parsed command and up to 32 raw arguments starting at the first flag, including option values; the payload is serialized and sent in a background POST.
- Telemetry is gated by a saved consent choice, an interactive prompt after a successful run, or the explicit TSUGA_TELEMETRY=1/true setting.
- The telemetry endpoint is /v1/cli-runs on the Tsuga API hosts.
Evidence against
- The manifest has no install lifecycle scripts; the telemetry runs as part of invoking the CLI.
- The prompt asks whether to send usage data, and users can later turn telemetry off.
- The default destination is Tsuga’s own API, with configured API hosts restricted by source checks.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
18 flaggeddist/cli.jsView file
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_oauth
severity = critical
line = 273
Critical
273patternName = github_server_token
severity = critical
line = 273
Critical
Secret Pattern
GitHub server-to-server token in dist/cli.js
dist/cli.jsFindings
9 Critical9 High2 Medium4 Low
CriticalCritical Secretdist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
HighChild Processdist/cli.js
HighSame File Env Network Executiondist/cli.js
HighCommand Output Exfiltrationdist/cli.js
HighTrigger Reachable Command Output Exfiltration
Affected versions and remediation
This report applies to @tsuga/cli@1.138.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.138.0 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.