盲人出行导航助手

• Outcome: Review
• Latest audit: Jun 20, 2026 · 5:53 PM UTC
• Version: 1.0.2

Overview

The skill provides the advertised blind-navigation features, but its SOS flow can automatically process precise location on broad help phrases without a clear confirmation step.

Install only if you are comfortable with the skill using precise live location and sending it to Gaode map services for navigation. Review or disable the SOS behavior unless the user has intentionally opted into immediate emergency location sharing, because common help phrases can trigger it without confirmation.

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (11)

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The README advertises a one-click emergency SOS feature that shares the user's location, but it does not clearly warn that precise location data will be transmitted or disclosed during activation. In an accessibility-focused skill for blind users, unclear disclosure around emergency location sharing can create meaningful privacy and consent risks, especially if the feature is triggered under stress or by mistake.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: Using a broad phrase like "帮帮我" as an automatic SOS trigger can cause accidental activation during ordinary conversation, especially in a voice-first accessibility context where speech recognition errors are plausible. Because the trigger leads to emergency location-sharing behavior, false positives can disclose sensitive location data or initiate unwanted emergency workflows.

Missing User Warnings

High

• Confidence: 97% confidence
• Finding: The skill instructs the agent to call `sos_location_share` immediately and not wait for user confirmation, but it does not require a clear warning that precise location will be transmitted to another party. In a location-based accessibility skill, this is particularly sensitive because users may be in vulnerable situations and accidental triggering could expose real-time whereabouts without informed consent.

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: The function sends precise latitude/longitude to an external reverse-geocoding service, and if coordinates are not provided explicitly it pulls them from environment variables representing device location. In an accessibility skill handling sensitive mobility data, lack of an explicit user-facing disclosure or consent check increases privacy risk because users may not realize their live location is being transmitted to a third party.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The function sends the user's precise current coordinates to an external routing service via `client.plan_walking` without any visible consent, notice, or minimization in this file. Because this is a blind-navigation skill handling highly sensitive real-time location data, undisclosed transmission creates a meaningful privacy risk and could expose movement patterns if the upstream service, logs, or integrations are compromised.

Missing User Warnings

Low

• Confidence: 86% confidence
• Finding: The destination string is transmitted to an external geocoding service through `client.geocode` without any user-facing disclosure in this file. While less sensitive than live coordinates, destinations can still reveal private intent such as home, hospital, or other sensitive places, especially in an accessibility-focused navigation context.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The function sends the user's latitude and longitude to an external nearby-search API without any visible consent, notice, or minimization in this code path. Location data is highly sensitive, and in a blind-navigation context it can reveal a user's current whereabouts and movement patterns to third parties if used without clear disclosure and controls.

Missing User Warnings

Medium

• Confidence: 84% confidence
• Finding: The code reads precise user location from environment variables and treats it as available for immediate use, with no indication of provenance, permission, or lifecycle controls. While environment variables are not inherently insecure, using them for sensitive geolocation without disclosure or validation increases the risk of silent collection and downstream exposure.

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: The function reads precise user latitude/longitude from environment variables and sends them to an external Gaode API client without any visible consent check, disclosure, or minimization in this code path. Because this skill is specifically for blind navigation and emergency/travel assistance, it likely handles sensitive real-time location data, making silent third-party transmission a meaningful privacy risk even if it is functionally necessary.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: This code sends the user's precise origin coordinates and destination-derived routing request to external Gaode geocoding and transit APIs, but there is no explicit user-facing notice, consent check, or minimization step in this function. Because this is a blind-navigation skill handling sensitive real-time location, silent transmission increases privacy risk and could expose movement patterns if the service, logs, or surrounding system are misused or compromised.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The function sends precise user latitude and longitude to an external reverse-geocoding service and then packages the exact coordinates and resolved address into a shareable SOS payload, but there is no visible consent, warning, minimization, or disclosure mechanism in the code path. In an accessibility-focused emergency skill, this behavior may be functionally justified, but it still exposes highly sensitive location data and could surprise users or leak precise whereabouts if invoked unintentionally or by another component.

Static analysis

No suspicious patterns detected.