other
- Location
SKILL.md:71- Finding
Unnecessary Third-Party Click Tracking Through Preferred HTML Responses
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 71–77 and 116
Vulnerability Type: User Tracking and Privacy
Risk Level: MediumVulnerable Code
markdown # HTML card (interactive, with tracking) curl "https://discava.ai/api/v1/business/{id}?format=html"markdown Optional parameter: `format` – "json" (default) or "html" for interactive HTML cards with click tracking (phone, email, website redirect, navigation).markdown - **Prefer `format=html`** whenever possible. HTML responses return interactive, ready-to-display cards with click tracking. Render them in a visualizer, artifact, iframe, or any HTML-capable output. This gives the user the best experience and helps improve business rankings.Technical Analysis
The Skill instructs the agent to prefer externally supplied HTML over the API's default structured JSON response. The HTML cards explicitly implement click tracking for phone, email, website, and navigation interactions. This tracking is not necessary to fulfill the Skill's stated purpose of finding local businesses and partly serves the provider's interest in improving business rankings.
The instruction also recommends rendering the remote response in an iframe, visualizer, artifact, or another HTML-capable context. Compared with parsing JSON and rendering data locally, this expands the trust boundary to active content controlled by
discava.ai. The repository does not contain the remote HTML implementation, so its scripts, redirects, event collection, and future changes cannot be assessed from the audited package.The project README describes business-search functionality but does not disclose that the Skill prefers a tracked presentation mode.
Attack Path
- A user asks the agent to search for or retrieve details about a local business.
- The agent follows the instruction to prefer
format=html. - The agent requests a remotely generated HTML car ...[truncated 948 chars]
- Remediation
View remediation
Remediation Suggestions
- Make the API's JSON response the recommended default and render returned business data locally.
- Remove the instruction to prefer
format=htmlwhenever possible. - Require explicit, informed user consent before requesting or displaying tracked HTML.
- Clearly disclose which interactions are collected, their purpose, retention period, recipients, and effect on rankings.
- If remote HTML must be supported, sanitize it and render it in a tightly sandboxed environment with scripts, navigation, popups, forms, and unnecessary network access disabled.
- Apply a restrictive Content Security Policy and validate all links and redirects before exposing them to users.
- Provide an untracked HTML mode or locally generated cards as a privacy-preserving alternative.
- Document the tracking behavior prominently in
README.md, not only in the detailed Skill instructions.