other
- Location
SKILL.md:39- Finding
Source Content May Be Disclosed to an Unverified Third-Party API
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 39-43
Vulnerability Type: Untrusted external service / potential information disclosure
Risk Level: MediumVulnerable Content:
markdown ## API Uses a web-based content API at https://extant-torrie-nonrepealable.ngrok-free.dev. Buy credits at /buy if the API returns a 402 response.Technical Analysis
The skill declares that content processing uses an externally hosted API on an opaque, temporary-looking
ngrok-free.devsubdomain. The documentation does not identify the service operator, provide privacy or retention terms, describe what information is transmitted, or require informed user consent before source content is submitted.The skill is intended to process blog posts, podcast transcripts, videos, and potentially internal memos. Such input may contain confidential, proprietary, personal, or unpublished information. Sending this material to an unverified service creates a third-party disclosure risk. The recommendation to purchase credits through the same endpoint additionally exposes users to an unverified payment destination.
The reviewed package contains no executable source code, so the exact request implementation, transport payload, server-side retention, and payment workflow cannot be verified from the available files. There is no evidence that the endpoint retrieves or executes code; therefore, this issue is not classified as remote payload execution.
Attack Path
- A user supplies private or proprietary source content to a web-connected agent using this skill.
- Following the skill documentation, the agent submits that content to the specified
ngrok-free.devAPI. - The external service operator receives the submitted content and associated request metadata.
- If the service is malicious, compromised, or inadequately secured, it may retain, inspect, reuse, or disclose that information.
- If an HTTP 402 response occurs, the user may also be dir ...[truncated 706 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the temporary or opaque tunnel URL with a stable domain controlled by a verified service operator.
- Clearly identify the API operator and publish privacy, retention, deletion, subprocessors, and security policies.
- Obtain explicit user consent before transmitting source content externally, including a clear description of the data and destination.
- Minimize transmitted data and redact credentials, personal information, internal material, and unrelated metadata before submission.
- Provide a local-processing option for sensitive content.
- Document request fields, authentication behavior, logging, retention periods, and deletion procedures.
- Apply strict TLS certificate validation, request timeouts, response-size limits, and destination allowlisting in any implementation that calls the API.
- Do not direct users to an unverified payment endpoint. Use a recognized payment processor on a stable, authenticated domain and clearly identify the merchant.
- Add warnings advising users not to submit confidential or regulated information unless suitable contractual and technical safeguards are in place.
