Back to skill

Security audit

Outreach And Prospecting

Security checks for vulnerabilities and agentic risk

Overview

This is a plain text outreach playbook with no code execution, hidden behavior, persistence, or credential access, though users should apply privacy and anti-spam rules when tracking prospects.

Installers should treat this as sales-outreach guidance, not an automated sending or compliance tool. Use it with consent, opt-out, privacy, platform, and anti-spam requirements in mind, and avoid storing unnecessary sensitive personal details in any pipeline notes.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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 (2)

Vague Triggers

Medium
Confidence
95% confidence
Finding
L003 lists triggers such as "prospecting", "find customers", "build a pipeline", and "find clients" without contextual limits or exclusion conditions. These phrases are broad enough to match ordinary business conversations, increasing the chance of unintended invocation.

Missing User Warnings

Medium
Confidence
84% confidence
Finding
The skill instructs users to collect, store, and revisit lead names, companies, contact dates, notes, and pipeline status without any privacy, consent, retention, or legal-compliance guidance. In an outreach context, this can normalize unnecessary processing of personal/contact data, lead to over-collection or prolonged retention, and increase risk of privacy-law violations or misuse of prospect information.

Static analysis

No suspicious patterns detected.