@tsuga/cli@1.129.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged process and network behavior implements consent-gated telemetry, not command-output theft. However, the telemetry payload can include user-supplied argument values, which the generic consent prompt does not specifically disclose, so this merits 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 TSUGA_TELEMETRY or accepts the interactive telemetry prompt; saved consent also enables later reports.
Impact
Argument values may contain user-supplied query or other sensitive data. The broad “usage data” prompt does not explain that argument values are included.
Mechanism
The CLI packages run metadata and spans, then starts a detached Node process to POST the payload to the API endpoint. The payload schema includes arguments from the first flag onward, including their values.
AI rationale
The flagged process and network behavior implements consent-gated telemetry, not command-output theft. However, the telemetry payload can include user-supplied argument values, which the generic consent prompt does not specifically disclose, so this merits a warning.
Evidence
dist/cli.js
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 CLI records run telemetry and sends it in a detached POST to its configured API endpoint after the telemetry consent check.
- The telemetry schema includes command-line arguments starting at the first flag, including their values.
- Telemetry can be enabled with TSUGA_TELEMETRY=1/true or through a prompt that describes the choice only as sending “usage data.”
Evidence against
- The manifest has no install, preinstall, or postinstall lifecycle scripts.
- The CLI’s telemetry check requires saved consent, the environment opt-in, or an interactive consent prompt; it does not send telemetry by default.
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.129.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.129.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.