@tsuga/cli@1.137.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 16h ago · by lpm-firewall-aiThe CLI’s telemetry gate requires saved consent, an explicit environment override, or an interactive prompt, but the submitted record includes raw flag values. Because the usage-data disclosure does not explain this collection, classify it as suspicious telemetry rather than malicious behavior.
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 command runs when telemetry is enabled by saved consent or TSUGA_TELEMETRY; on the first successful interactive command, the CLI asks whether to send usage data.
Impact
Tsuga’s API may receive private query values or credentials supplied as flag values, beyond what the usage-data prompt describes.
Mechanism
The CLI gathers up to 32 arguments from the first flag onward, including their values, then sends the run record in a detached process to Tsuga’s CLI-runs API.
AI rationale
The CLI’s telemetry gate requires saved consent, an explicit environment override, or an interactive prompt, but the submitted record includes raw flag values. Because the usage-data disclosure does not explain this collection, classify it as suspicious telemetry rather than malicious behavior.
Evidence
dist/cli.jsREADME.md~/.config/tsuga/config.json$XDG_CONFIG_HOME/tsuga/config.json
Network endpoints1
api.tsuga.com/v1/cli-runs
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI records up to 32 raw arguments from the first flag onward, and its telemetry schema specifies that these include argument values.
- After the telemetry gate allows reporting, the CLI serializes the run record and starts a detached Node process to send it.
- The reporter POSTs the serialized record to the Tsuga CLI-runs endpoint.
- The prompt and README describe the collection as “usage data” but do not disclose that flag values are sent.
Evidence against
- There are no lifecycle scripts; telemetry runs as part of a CLI command.
- The CLI asks for consent on the first successful interactive command, saves the answer, and supports turning telemetry off; an environment variable can override the saved setting.
- The endpoint is on Tsuga’s own API host, and the reported fields also include ordinary command, runtime, and platform usage data.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
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.137.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.137.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.