Back to skill

Security audit

Substack Newsletter Coach

Security checks for vulnerabilities and agentic risk

Overview

This is a plain newsletter-coaching instruction file with no code, credential access, persistence, or hidden behavior.

Installers should understand that this skill may be invoked for general newsletter-related requests, but its behavior is limited to strategic writing and growth advice. Review any business or monetization recommendations before acting on them, especially pricing, migration, or paid-tier decisions.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The description says the skill triggers on terms including "newsletter" and "paid conversion," which are broad phrases that can appear in many ordinary writing, marketing, or business conversations outside the intended Substack/newsletter-coaching context. The file also does not provide exclusion conditions or negative examples to narrow when these triggers should not activate.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.