@tsuga/cli@1.106.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe CLI has consent-gated telemetry, but its argument collection includes strings after the first option, potentially including sensitive option values. The generic usage-data prompt does not disclose that collection, so this warrants a warning rather than a block.
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 CLI run when telemetry consent is saved, accepted at the prompt, or enabled with TSUGA_TELEMETRY=1.
Impact
Option values may contain sensitive user input that the generic usage-data consent prompt does not describe.
Mechanism
The CLI copies arguments from the first option onward into telemetry and submits the report to its configured Tsuga API endpoint.
AI rationale
The CLI has consent-gated telemetry, but its argument collection includes strings after the first option, potentially including sensitive option values. The generic usage-data prompt does not disclose that collection, so this warrants a warning rather than a block.
Evidence
dist/cli.js~/.config/tsuga/config.json
Network endpoints1
Configured Tsuga API endpoint (default api.tsuga.com; TSUGA_API_URL can override it)
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Telemetry copies command-line strings from the first option onward into the `cli.flags` field, which can include option values.
- On a CLI run, the package reports telemetry after consent and sends the payload to the configured Tsuga API endpoint using a detached Node process.
- Without saved consent, telemetry requires an interactive prompt or explicit `TSUGA_TELEMETRY=1` opt-in.
Evidence against
- The manifest declares no install or lifecycle scripts.
- Telemetry is not sent unless consent is saved, the user accepts the prompt, or the user explicitly opts in through the environment variable.
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.106.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.106.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.