@tsuga/cli@1.113.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe CLI’s opt-in telemetry collects a bounded slice of command-line arguments, while its consent prompt only describes this as “usage data.” This warrants a warning for potentially identifying telemetry; the consent gate and absence of install-time behavior do not support a malicious verdict.
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 user runs the CLI after enabling telemetry or accepting its prompt; the report is sent after a successful command.
Impact
A user may unknowingly share identifying or sensitive text entered as command-line arguments with the telemetry service.
Mechanism
The CLI collects command names, a bounded slice of arguments, and runtime metadata, then sends a report to its resolved API URL. The prompt does not explain that arguments are included.
AI rationale
The CLI’s opt-in telemetry collects a bounded slice of command-line arguments, while its consent prompt only describes this as “usage data.” This warrants a warning for potentially identifying telemetry; the consent gate and absence of install-time behavior do not support a malicious verdict.
Evidence
dist/cli.js
Network endpoints1
api.tsuga.com
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- When CLI execution finishes, the telemetry reporter builds a report and sends it only if its consent check passes.
- Telemetry captures a bounded slice of command-line arguments beginning at the first option, including option values that may contain paths or query text.
- The consent prompt says only “Send usage data?” and offers a setting to change telemetry later; it does not specify that command-line arguments are collected.
- The default API host is api.tsuga.com.
Evidence against
- The manifest declares no install, preinstall, or postinstall hook.
- Telemetry is gated by stored consent, an interactive prompt, or the explicit TSUGA_TELEMETRY=1/true setting.
- The CLI is described as a resource-management tool, and the telemetry code sends usage reports rather than executing an unrelated payload.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
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.113.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.113.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.