@tsuga/cli@1.116.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI has a consent gate, but its telemetry includes command-line flag values that the prompt does not specifically disclose. Since sending is gated by consent and targets the package’s API, this is suspicious telemetry rather than a clear malicious attack.
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 run when telemetry consent is enabled or the user approves the prompt.
Impact
Flag values such as queries may contain user-supplied data that the general usage-data prompt does not specifically disclose.
Mechanism
The CLI includes arguments from the first flag onward in its run telemetry and posts the payload to its configured API endpoint.
AI rationale
The CLI has a consent gate, but its telemetry includes command-line flag values that the prompt does not specifically disclose. Since sending is gated by consent and targets the package’s API, this is suspicious telemetry rather than a clear malicious attack.
Evidence
dist/cli.jsREADME.md
Network endpoints2
api.tsuga.com/v1/cli-runsapi.tsuga-staging.com/v1/cli-runs
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The telemetry payload includes command-line arguments from the first flag onward, including their values; its example includes a query value.
- The CLI sends run telemetry only after its consent check succeeds, to its configured API endpoint.
- The documented consent prompt asks whether to send “usage data” but does not explain that flag values are included.
Evidence against
- The package declares no install lifecycle scripts; its CLI is exposed as a command-line binary.
- Users can answer the telemetry prompt, change the saved setting, or override it with TSUGA_TELEMETRY.
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.116.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.116.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.