ClawHub
Back to skill

Security audit

Tmux Session Tool Free

Security checks across malware telemetry and agentic risk

Overview

This skill is a straightforward tmux helper, but it can read terminal history and send input into live terminal panes if the user points it there.

Install only if you are comfortable giving the agent local tmux command access. Before sending keys, confirm the exact session and pane, avoid panes containing secrets, and redact captured terminal output before sharing it in prompts, logs, or reports.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The skill can inject keystrokes into a live tmux pane, which can execute commands or alter an active assistant/session state, but the description does not prominently warn about this side effect. In practice, an operator may treat it as read-only session inspection and unintentionally send destructive or sensitive commands to the wrong target.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The skill captures and dumps tmux pane contents, which may include secrets, prompts, tokens, user data, or proprietary code, yet it lacks a privacy/sensitivity warning. Because tmux buffers often contain unredacted terminal history, encouraging capture/export without warning increases the chance of accidental disclosure.

Ssd 3

Medium
Confidence
95% confidence
Finding
The skill instructs the agent to read and report recent tmux pane contents, including prior user inputs and assistant outputs, which can expose sensitive conversation history in plain text. In a real developer session this may include credentials, internal code, incident details, customer data, or privileged instructions from other tools.

Ssd 3

Medium
Confidence
95% confidence
Finding
The reporting example explicitly tells the agent to include prior user instructions and assistant replies in its output, normalizing disclosure of session contents. This makes leakage more likely because operators may copy sensitive terminal history into responses, logs, or downstream systems without realizing the privacy impact.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.