registry / @tsuga/cli / 1.111.0
@tsuga/cli@1.111.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged network and child-process behavior implements usage telemetry, and the CLI asks for consent before sending it. The package is presented as a resource-management CLI, consistent with its entry point and telemetry 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 user accepts the usage-data prompt or enables telemetry through configuration or TSUGA_TELEMETRY.
Impact
Telemetry is sent only after consent; the inspected code does not show credential theft or unrelated command-output exfiltration.
Mechanism
After consent, the CLI sends run metadata and spans to the resolved Tsuga API URL using a detached Node process.
AI rationale
The flagged network and child-process behavior implements usage telemetry, and the CLI asks for consent before sending it. The package is presented as a resource-management CLI, consistent with its entry point and telemetry behavior.
Evidence
CLI telemetry consent configuration
Network endpoints1
Resolved Tsuga API URL (M8.url)
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package describes itself as a CLI for managing resources and exposes dist/cli.js as its command entry point.
- The CLI asks whether to send usage data, saves the answer, and provides an on/off setting.
- Run telemetry is sent only after the consent check succeeds; it includes run metadata and spans.
Evidence against
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.111.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.111.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.