@tsuga/cli@1.122.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 2d ago · by lpm-firewall-aiNo malicious behavior was identified. The opt-in telemetry report includes command argument values, which may exceed what users understand from the generic “usage data” prompt, so this warrants 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
After a CLI run when telemetry consent is enabled, including through TSUGA_TELEMETRY=1.
Impact
Arguments such as query values may contain user data beyond basic usage metrics; the consent prompt describes this generally as usage data.
Mechanism
The CLI gathers command arguments and run spans, then posts a report to the Tsuga API.
AI rationale
No malicious behavior was identified. The opt-in telemetry report includes command argument values, which may exceed what users understand from the generic “usage data” prompt, so this warrants a warning.
Evidence
dist/cli.js
Network endpoints1
/v1/cli-runs
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI records command-line argument values in its run report, including query flags and their values.
- Run reporting is gated by saved consent, an interactive consent prompt, or TSUGA_TELEMETRY=1; users can change consent later.
- The report is sent to the Tsuga API at /v1/cli-runs and includes run metadata and recorded spans.
Evidence against
- The manifest exposes a CLI entry point and declares no install lifecycle scripts.
- The telemetry path checks consent before sending the report.
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.122.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.122.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.