@tsuga/cli@1.112.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe report is gated by consent and goes to the package’s own API, but it collects raw command-line flag values, which may contain identifying or sensitive details. That collection exceeds routine usage metrics, so this warrants a warning rather than a clean verdict.
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 already saved, or an interactive user accepts the usage-data prompt; TSUGA_TELEMETRY=1 also enables it.
Impact
Flag values may contain sensitive or identifying details; sending these to the package’s own service creates a privacy risk.
Mechanism
The CLI includes command-line arguments from the first flag onward, including their values, in a usage report and sends it through a detached Node process to the configured API URL.
AI rationale
The report is gated by consent and goes to the package’s own API, but it collects raw command-line flag values, which may contain identifying or sensitive details. That collection exceeds routine usage metrics, so this warrants a warning rather than a clean verdict.
Evidence
dist/cli.js
Network endpoints1
api.tsuga.com
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The telemetry schema includes up to 32 command-line arguments from the first flag onward, including their values.
- After the telemetry check passes, the CLI sends the report in a detached child process to its configured API URL.
- Telemetry requires saved consent or an interactive prompt; the prompt describes it as sending “usage data.”
- The default API URL is https://api.tsuga.com.
Evidence against
- The package is a CLI for managing Tsuga resources, consistent with reporting usage to its own service.
- The manifest declares no install, preinstall, or postinstall lifecycle hook.
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.112.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.112.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.