Back to skill

Security audit

Ecommerce Customer Journey Mapper

Security checks for vulnerabilities and agentic risk

Overview

This skill generates a heuristic ecommerce customer journey report from user-provided text and does not access external accounts, APIs, files, or persistent storage.

Installers should understand that the output is advisory and heuristic, not based on live analytics or external customer data. Users should provide only the business notes they are comfortable sharing with the agent running the skill.

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
  • 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 (2)

Natural-Language Policy Violations

Medium
Confidence
96% confidence
Finding
The stage-detection keywords are explicitly limited to English and Chinese terms, which creates a built-in language constraint in the skill's behavior. Because the file provides no opt-in, fallback, or user-selectable locale handling, this is a natural-language policy concern under the language/locale rule.

Natural-Language Policy Violations

Low
Confidence
94% confidence
Finding
The manifest sets "language": "en", which expresses a fixed language requirement. Under the policy criteria, a forced language setting without an explicit user choice or documented justification can be a locale-policy violation.

Static analysis

No suspicious patterns detected.