registry / @tsuga/cli / 1.49.0
@tsuga/cli@1.49.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe source supports a warning for first-party agent plugin lifecycle behavior, including default automatic updates, and explicit telemetry configuration. User-command activation and the absence of npm install hooks do not support blocking this release as malicious.
Static reason
One or more suspicious static signals were detected.
Trigger
Running tsuga install plugin claude-code or codex, or tsuga setup claude-code or codex.
Impact
Future plugin updates can change agent capabilities, and configured telemetry can expose sensitive conversation content to the selected recipient.
Mechanism
The CLI invokes agent plugin commands and writes agent settings. Claude marketplace auto-updates and telemetry prompt inclusion default to enabled, with disabling flags.
AI rationale
The source supports a warning for first-party agent plugin lifecycle behavior, including default automatic updates, and explicit telemetry configuration. User-command activation and the absence of npm install hooks do not support blocking this release as malicious.
Evidence
dist/cli.js~/.claude/settings.json~/.codex/config.toml
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Explicit CLI commands install Tsuga plugins from tsuga-dev/agent-plugins into Claude Code and Codex.
- Claude plugin installation defaults to enabling marketplace auto-updates; --no-auto-update skips the saved setting.
- Explicit telemetry setup writes agent configuration using a caller-selected endpoint and ingestion key.
- Telemetry setup includes user prompts by default; Claude configuration also enables tool details and content.
Evidence against
- package.json has no preinstall, install, or postinstall hook and no runtime self-dependency.
- Agent changes are activated by explicit CLI commands, and configuration writes create backups.
- Inspected API credential storage is keyed by API destination; no concrete credential theft was identified.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscation
Source & flagged code
13 flaggeddist/cli.jsView file
239patternName = github_pat
severity = critical
line = 239
Critical
239patternName = github_pat
severity = critical
line = 239
Critical
239patternName = github_oauth
severity = critical
line = 239
Critical
239patternName = github_server_token
severity = critical
line = 239
Critical
Findings
9 Critical4 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
HighCredential Redirect Persistencedist/cli.js
HighSecret Patterndist/cli.js
HighSecret Patterndist/cli.js
HighSecret Patterndist/cli.js
Affected versions and remediation
This report applies to @tsuga/cli@1.49.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.49.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.