Back to skill

Security audit

Market Research

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent market-research guidance skill made of Markdown instructions, with no executable code or hidden access behavior found.

Installers should treat this as a market-research assistant skill: it may lead the agent to search public sources and compare competitors when asked, but the reviewed artifacts do not add code execution, persistence, secret handling, or hidden data access.

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
  • System Prompt LeakageDirect Leakage, Indirect Extraction, Tool-Based Exfiltration
  • 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)

Direct Prompt Extraction

High
Category
System Prompt Leakage
Confidence
85% confidence
Finding

Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.

Content

Scanner excerpt · evidence-grading.md (reported line 22)May include surrounding context.

md
| Market entry recommendation | High confidence on demand, competition, and reachability |
| Expansion timing | High confidence on segment fit and local constraints |

## Output Rule

Every major conclusion should include:
- the claim

Static analysis

No suspicious patterns detected.