@tsuga/cli@1.99.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 6d ago · by lpm-firewall-aiThis is a legitimate Tsuga management CLI, and its usage reporting is opt-in. However, the report copies raw flag tokens, which can expose sensitive option values without the consent prompt specifically explaining that behavior; warn about the telemetry scope.
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 command when telemetry is enabled by saved consent or TSUGA_TELEMETRY=1; otherwise the CLI asks interactively.
Impact
Sensitive values supplied as flags, such as an operation API key, may be included in usage telemetry. The generic usage-data prompt does not specifically disclose that flag values can be sent.
Mechanism
The report copies flag tokens from argv into its telemetry payload and sends it in a detached Node process via HTTP POST.
AI rationale
This is a legitimate Tsuga management CLI, and its usage reporting is opt-in. However, the report copies raw flag tokens, which can expose sensitive option values without the consent prompt specifically explaining that behavior; warn about the telemetry scope.
Evidence
dist/cli.jsREADME.mdXDG_CONFIG_HOME/tsuga/config.json~/.config/tsuga/config.json
Network endpoints2
api.tsuga.comapi.tsuga-staging.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI advertises a one-time interactive prompt asking whether to send usage data, with saved and environment-variable controls.
- The telemetry payload copies raw command-line flag tokens from argv, which can include user-supplied values.
- The CLI accepts an operation API key as a command-line option, so a key supplied there can be included among those tokens.
- After consent, the CLI starts a detached Node process that POSTs the telemetry payload.
Evidence against
- Telemetry is sent only when consent is enabled; an interactive user is prompted and can change the saved choice or override it with TSUGA_TELEMETRY.
- The API URL is restricted to Tsuga’s own API hosts or localhost.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
18 flaggeddist/cli.jsView file
268patternName = github_pat
severity = critical
line = 268
Critical
268patternName = github_pat
severity = critical
line = 268
Critical
268patternName = github_oauth
severity = critical
line = 268
Critical
268patternName = github_server_token
severity = critical
line = 268
Critical
Findings
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.99.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.99.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.