Back to skill

Security audit

PC*Miler

Security checks for vulnerabilities and agentic risk

Overview

This skill is a simple PCMiler API reference for routing and geocoding, with expected network use and API-key authentication but no bundled code or persistence.

Before installing, confirm you are comfortable sending addresses, coordinates, route stops, and your PCMiler API key to PCMiler. Use an appropriately scoped key, avoid embedding secrets in shared logs or scripts, and do not submit sensitive location data unless that sharing is approved.

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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The documentation demonstrates sending precise route stops and geocoded location data to an external API, but it does not warn users that sensitive location information will leave the local environment. In a routing skill, this data flow is expected, yet the absence of a privacy notice can cause unintentional disclosure of personal, customer, or operational movement data.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

The setup section requires an API key for outbound requests but does not clearly warn that the credential will be sent to a third-party service as part of authenticated network calls. While this is normal for an API client, users should be informed that their key is used in external requests so they can evaluate trust, scope, and key management risks.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.