registry / @tsuga/cli / 1.98.0
@tsuga/cli@1.98.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged network and process behavior implements CLI usage telemetry. It is gated by user consent and targets the package’s own Tsuga API, so the evidence supports clean behavior.
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 after telemetry consent is enabled or granted in the interactive prompt.
Impact
Usage telemetry reaches the Tsuga service; the source does not show unrelated collection or an unauthorized account action.
Mechanism
The CLI sends a JSON usage payload and spans in a detached Node process to the configured Tsuga API URL.
AI rationale
The flagged network and process behavior implements CLI usage telemetry. It is gated by user consent and targets the package’s own Tsuga API, so the evidence supports clean behavior.
Network endpoints1
api.tsuga.com (default; API URL can be configured)
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package is a CLI for managing Tsuga resources.
- Run telemetry is gated by saved consent or an interactive “Send usage data?” prompt; it is not sent when the CLI is non-interactive or the command exits unsuccessfully.
- The telemetry sender posts a JSON payload to the Tsuga API URL, which defaults to https://api.tsuga.com.
- The prompt describes the data as usage data and lets users change the setting later.
Evidence against
- The bundle uses a detached Node process to send telemetry, and the payload includes run details and spans.
- The manifest declares no install lifecycle scripts.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
18 flaggeddist/cli.jsView file
268patternName = github_pat
severity = critical
line = 268
Critical
268patternName = github_pat
severity = critical
line = 268
Critical
268patternName = github_oauth
severity = critical
line = 268
Critical
268patternName = github_server_token
severity = critical
line = 268
Critical
Findings
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.98.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.98.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.