Back to skill

Security audit

Filewatch

Security checks for vulnerabilities and agentic risk

Overview

This skill is a local Filewatch reference tool that only prints documentation and does not access credentials, network resources, or persistent system settings.

This appears safe to install as a simple offline reference skill. Be aware that the content is generic and has a small command-name inconsistency, so use it as reference material rather than authoritative Filewatch tooling.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · scripts/script.sh (reported line 64)May include surrounding context.

sh
## Prerequisites
- Basic understanding of devtools concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
92% confidence
Finding

The cheatsheet table documents an essential command named 'troubleshooting', but the actual command dispatcher only implements 'debugging' and has no 'troubleshooting' case. This is an active contradiction between embedded documentation and executable behavior, not merely an omission.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.