Back to skill

Security audit

Localization Planner

Security checks for vulnerabilities and agentic risk

Overview

This is a read-only planning skill for ecommerce localization, and its locale guidance fits the stated purpose without hidden execution or data access.

Installers should understand this skill offers business localization guidance, including country-specific language, payment, calendar, and compliance considerations. Verify legal, compliance, payment-share, and holiday details with current in-market sources before acting on the plan.

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

The checklist requires content to be translated by a native speaker and to match the local market's tone, which imposes locale-specific language behavior as a requirement. Because the file does not present this as an optional, user-selected, or explicitly justified regional constraint, it can be read as forcing a specific language/locale approach.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
80% confidence
Finding

The markdown directs language handling in specific locales, such as 'Arabic and English' for the UAE and 'Portuguese vs Brazilian Portuguese' for Brazil, as default planning assumptions. This can be read as forcing locale decisions rather than explicitly offering user choice or opt-in, which may conflict with language/locale policy expectations.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.