Back to skill

Security audit

coffee-brew-lab

Security checks for vulnerabilities and agentic risk

Overview

This coffee-brewing skill is purpose-aligned and only keeps an optional local brew log for the recipe and analysis features it advertises.

Before installing, be aware that using the log commands will create or update a local JSON file containing your brew settings and scores. Use the documented --store option if you want that file somewhere specific.

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
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • 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
Findings (1)

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
87% confidence
Finding

The skill advertises executable command usage and persistent local storage via brew_log.json, implying file read/write behavior, but it does not declare any explicit tool scope such as permissions or allowed-tools. Even though the skill is coffee-related and not overtly dangerous, missing scope boundaries can cause an agent runtime to grant broader filesystem access than intended or make the skill's capabilities ambiguous to reviewers and enforcement systems.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.