@tsuga/cli@1.26.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has a real, user-invoked AI-agent configuration capability with potentially sensitive telemetry collection, but source inspection found no automatic lifecycle trigger or covert exfiltration path. This warrants a warning rather than a publication block.
Static reason
One or more suspicious static signals were detected.
Trigger
The user runs tsuga setup or tsuga install plugin.
Impact
User prompts, tool content, and telemetry may be sent to the configured Tsuga endpoint.
Mechanism
Explicit AI-agent configuration and plugin installation.
AI rationale
The package has a real, user-invoked AI-agent configuration capability with potentially sensitive telemetry collection, but source inspection found no automatic lifecycle trigger or covert exfiltration path. This warrants a warning rather than a publication block.
Evidence
dist/cli.js~/.claude/settings.json~/.codex/config.toml
Network endpoints2
api.tsuga.comregistry.npmjs.org
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- Explicit setup commands patch local Claude Code and Codex telemetry configuration, with prompts included by default.
- Explicit plugin-install commands invoke the local Claude or Codex CLI and enable Claude marketplace auto-update.
- The CLI sends authenticated API requests using a saved or environment-supplied Tsuga credential.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- The agent configuration changes are reachable only through named user commands, not package installation or import.
- The npm update check only queries the package's own registry record and prints an update notice.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
17 flaggeddist/cli.jsView file
51patternName = github_pat
severity = critical
line = 51
Critical
51patternName = github_pat
severity = critical
line = 51
Critical
51patternName = github_oauth
severity = critical
line = 51
Critical
51patternName = github_server_token
severity = critical
line = 51
Critical
Findings
9 Critical8 High3 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
HighSandbox Evasion Gated Capabilitydist/cli.js
Affected versions and remediation
This report applies to @tsuga/cli@1.26.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.26.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.