Back to skill

Security audit

Leaflet Maps

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Leaflet mapping helper with no hidden code execution, credential handling, persistence, or destructive behavior.

Safe to install for Leaflet web map help. Review tile-provider terms, attribution, and token handling when using generated examples, especially for production maps or private tile services.

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

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The description says to use the skill when the user asks for 'Leaflet code, OpenStreetMap/XYZ tile integration, 2D web map debugging, or Leaflet migration guidance.' Parts of this trigger scope, especially '2D web map debugging,' are broad and lack explicit exclusion conditions, which could cause invocation for non-Leaflet mapping tasks.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
77% confidence
Finding

The manifest embeds '中文触发' phrases as activation text, which introduces a language-specific trigger policy without explaining whether multilingual triggering is optional or user-selected. That can be a minor locale-policy concern because the file specifies a particular language behavior rather than presenting language support as an opt-in choice.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.