Back to skill

Security audit

Global Ads Helper

Security checks for vulnerabilities and agentic risk

Overview

This skill provides global advertising planning guidance and does not request privileged access, run code, or persist anything.

Use this as planning support for global paid advertising. Review assumptions, market data, budgets, compliance constraints, and ROI forecasts before acting, especially because ad platform rules and country-specific legal requirements can change.

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
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger keywords are broad generic marketing terms like 'market,' 'strategy,' 'revenue,' and 'scale,' which can cause the skill to activate for loosely related requests outside its intended scope. This creates prompt-routing ambiguity and may lead to inappropriate invocation, lower-quality outputs, or accidental application of this skill to contexts with different assumptions or compliance needs.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

The example "Launch in 3 English-speaking markets" introduces a language-based constraint in the skill's natural-language guidance. Because the file does not frame this as optional, user-selected, or regionally required, it can be read as steering outputs toward a specific language/locale preference.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.