@tsuga/cli@1.45.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has an explicit user-invoked capability to alter LLM CLI telemetry configuration and enable prompt export. This warrants a warning for agent capability abuse, while the available source does not prove malware or covert credential theft.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs a Tsuga setup command for a supported LLM CLI.
Impact
Future agent telemetry, potentially including prompts, can be sent to the endpoint selected by the user. No confirmed covert exfiltration surface was established.
Mechanism
The command writes agent configuration with a caller-provided telemetry endpoint and ingestion key; prompt telemetry is enabled unless disabled.
AI rationale
The package has an explicit user-invoked capability to alter LLM CLI telemetry configuration and enable prompt export. This warrants a warning for agent capability abuse, while the available source does not prove malware or covert credential theft.
Evidence
dist/cli.js~/.codex/config.toml~/.claude/settings.json
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package exposes a CLI entrypoint and has no install-time lifecycle hook in its manifest.
- The setup options accept an OTLP endpoint and ingestion key and enable prompt inclusion by default.
- The explicit Codex setup command rewrites the local OTEL configuration, including a caller-supplied endpoint and key.
Evidence against
- The configuration is reached through named CLI setup commands, not during package installation.
- The endpoint and ingestion key are supplied by the caller, so static source does not establish covert credential theft or a package-controlled recipient.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
13 flaggeddist/cli.jsView file
238patternName = github_pat
severity = critical
line = 238
Critical
238patternName = github_pat
severity = critical
line = 238
Critical
238patternName = github_oauth
severity = critical
line = 238
Critical
238patternName = github_server_token
severity = critical
line = 238
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.45.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.45.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.