T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:25- Finding
Excessive Tool Permissions Violate Least-Privilege Principles
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to be a local hashing and logging helper, but it asks for broad command and file authority and includes unclear callback/API behavior.
Review before installing. Use this only in a tightly sandboxed environment, avoid sensitive inputs unless you know where logs are written, disable or ignore callback/API behavior unless explicitly needed, and do not run it with administrator privileges for normal use.
SKILL.md:25Excessive Tool Permissions Violate Least-Privilege Principles
The skill is presented as a local-only, self-evaluating content-addressing tool, but the documented interface includes a callback URL and later references external API behaviors. This mismatch can cause users or orchestrators to send data off-host under the false assumption that processing is purely local, creating privacy, policy, and trust-boundary risks.
The documentation exposes callback/API-style network behavior without a clear privacy or transmission warning. Users may provide sensitive content for hashing/logging while unaware that metadata or payloads could be sent to external services, which is especially risky because the skill markets itself as a local auditing utility.
The skill instructs users to append records to a local log file but does not clearly warn that it performs persistent local writes. In agent environments, silent file creation or modification can violate user expectations, overwrite sensitive locations if paths are configurable elsewhere, or create audit/privacy issues through retained data.
The documentation says the free edition lacks endpoint validation, yet other sections discuss API authentication failures, rate limits, timeouts, and callback-driven remote interactions. These contradictory claims obscure the real attack surface and may lead operators to deploy the skill without appropriate egress controls, secrets handling, or monitoring.
The skill repeatedly frames itself as local append-only logging with no external storage, but later advertises API integration and command execution as core capabilities. Combining undisclosed exec and external communication increases the risk of unintended code execution, data exfiltration, and operator misuse because the documented trust boundaries are inconsistent.
No suspicious patterns detected.