@tsuga/cli@1.100.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI’s telemetry is gated by opt-in, so this is not malicious under the stated rules. However, it includes unfiltered option values that could contain sensitive data, while the consent prompt only says “Send usage data?”, so the telemetry 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 user enables telemetry or accepts the interactive usage-data prompt; reports are sent after CLI runs.
Impact
Sensitive values supplied as command-line options could be disclosed to Tsuga, beyond what the generic usage-data prompt describes.
Mechanism
The CLI collects tokens from its arguments starting at the first option and posts run data to the telemetry endpoint. Option values are not filtered before collection.
AI rationale
The CLI’s telemetry is gated by opt-in, so this is not malicious under the stated rules. However, it includes unfiltered option values that could contain sensitive data, while the consent prompt only says “Send usage data?”, so the telemetry warrants a warning.
Evidence
dist/cli.js~/.config/tsuga/config.json or $XDG_CONFIG_HOME/tsuga/config.json (telemetry consent)
Network endpoints1
api.tsuga.com/v1/cli-runs
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The package is a Tsuga resource-management CLI whose executable is dist/cli.js.
- The run-reporting endpoint is described as recording CLI runs only for clients that opted in.
- Telemetry copies command-line tokens starting at the first option into the report without filtering their values; those values could include sensitive input.
- Sending is gated by saved consent, an interactive prompt, or the TSUGA_TELEMETRY setting, but the prompt does not explain that option values are collected.
Evidence against
- package.json declares no install or lifecycle scripts.
- The report goes to Tsuga’s own API endpoint and is sent only after telemetry consent or opt-in.
- The CLI provides a setting to turn usage reporting off.
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.100.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.100.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.