Back to skill

Security audit

Fishing

Security checks for vulnerabilities and agentic risk

Overview

This skill keeps a local fishing journal and recommendation memory in a clearly disclosed ~/fishing folder, with no executable code or network data flow found.

Install only if you are comfortable keeping fishing history, locations, gear inventory, and optional license notes in local files under ~/fishing/. Review what gets recorded before sharing precise spots or personal details.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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 (2)

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The skill explicitly instructs the agent to update files in the user's home directory after a user reports a catch, but it does not require explicit user confirmation before modifying local data. Even though the writes are limited to the fishing memory store, silent or automatic file modification can violate user expectations, create integrity issues, and be abused by an agent that over-applies 'proactive' behavior.

Missing User Warnings

Low
Confidence
86% confidence
Finding
This markdown file instructs the user to create a directory and multiple files under `~/fishing/`, which affects user data on the local system. The document does not include any warning or disclosure about these filesystem changes or that the files will be created on first use.

Static analysis

No suspicious patterns detected.