@tsuga/cli@1.110.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 3d ago · by lpm-firewall-aiThis is consent-gated telemetry to the package’s API, so the evidence does not support a malicious verdict. However, it includes raw command-line flag values, which can contain identifying or sensitive data; classify it as suspicious telemetry.
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
After a successful CLI run when telemetry consent is saved, TSUGA_TELEMETRY=1 is set, or the user agrees to an interactive prompt.
Impact
Command arguments may contain identifying or sensitive values, which can be sent with usage telemetry.
Mechanism
The CLI builds a run report containing command-line arguments and sends it to the configured Tsuga API URL.
AI rationale
This is consent-gated telemetry to the package’s API, so the evidence does not support a malicious verdict. However, it includes raw command-line flag values, which can contain identifying or sensitive data; classify it as suspicious telemetry.
Evidence
dist/cli.js
Network endpoints5
api.tsuga.comapi.tsuga-staging.comlocalhost127.0.0.1[::1]
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The telemetry builder captures up to 32 command-line arguments beginning at the first flag, retaining their values.
- When reporting is enabled, the CLI sends a run report to its configured API URL using a detached Node process.
- The source identifies api.tsuga.com and api.tsuga-staging.com as allowed API hosts.
Evidence against
- The package declares no install, preinstall, or postinstall hook.
- Run reporting requires saved consent, TSUGA_TELEMETRY=1, or an interactive consent prompt after a successful run.
- The report is sent to the configured Tsuga API endpoint, and the CLI labels it usage data.
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.110.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.110.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.