@tsuga/cli@1.109.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe CLI has disclosed, opt-in runtime telemetry, but its payload includes command-line arguments and their values without describing that collection in the consent prompt or README. This is suspicious telemetry, not evidence of credential theft or malicious execution.
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 command succeeds, when telemetry consent is enabled by the prompt, saved setting, or TSUGA_TELEMETRY=1.
Impact
Arguments can contain user queries or other identifying details; the consent prompt and README do not specify that arguments are collected.
Mechanism
The CLI captures arguments from the first flag onward, including values, and posts telemetry to /v1/cli-runs.
AI rationale
The CLI has disclosed, opt-in runtime telemetry, but its payload includes command-line arguments and their values without describing that collection in the consent prompt or README. This is suspicious telemetry, not evidence of credential theft or malicious execution.
Evidence
dist/cli.jsREADME.md
Network endpoints1
api.tsuga.com/v1/cli-runs
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package exposes dist/cli.js as its tsuga command entry point.
- The README says telemetry consent is requested after the first successful interactive command; TSUGA_TELEMETRY can override the saved choice.
- The telemetry schema explicitly includes command-line arguments from the first flag onward, with their values.
- The CLI sends the telemetry payload to the /v1/cli-runs endpoint in a detached process.
- The bundled CLI defaults to https://api.tsuga.com.
Evidence against
- Telemetry is opt-in through an interactive prompt or TSUGA_TELEMETRY=1; TSUGA_TELEMETRY=0 disables it.
- The CLI describes this collection as usage data and sends it to the package's own service.
- No install lifecycle scripts are declared.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscation
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.109.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.109.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.