Security audit

Recipe Log Deal Update

Security checks for vulnerabilities and agentic risk

Overview

This recipe does what it says: it helps append a deal update to a specific Google Sheets sales pipeline, with the main risk being accidental spreadsheet changes.

Before running it, confirm the target Sales Pipeline spreadsheet and Pipeline tab are correct, replace the example row with the actual deal values, and consider reading the sheet first to avoid duplicate or mistaken entries.

A.I.G

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

SkillSpector

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 (1)

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The skill performs a persistent write to a Google Sheets sales tracker by appending a new row, but it does not warn the user that execution will modify business data. In a sales workflow this is expected behavior, yet the lack of an explicit confirmation or warning increases the risk of accidental data changes, duplicate entries, or unintended updates to a production tracking sheet.
Content: No source excerpt is available for this finding.