other
- Location
SKILL.md:15- Finding
Unrestricted Transmission of Sensitive Phone Call Data to a Third-Party Backend
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15-45
Vulnerability Type: Privacy and Sensitive Data Disclosure
Risk Level: MediumThe skill instructs the agent to collect phone-call details—including caller identity, company affiliation, business concerns, agreements, deadlines, and emotional cues—and transmit them to an externally hosted Supabase backend.
bash curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-remember \ -H "Authorization: Bearer $BLUECOLUMN_API_KEY" \ -H "Content-Type: application/json" \ -d '{"text": "CALL 7/31 14:20 with Marcus (Acme): asked about the Builder plan pricing. Concern: overage fees. Agreed: I email pricing sheet today; he decides by Friday. Tone: friendly, slightly rushed.", "title": "call - Marcus 7/31"}'bash curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-recall \ -H "Authorization: Bearer $BLUECOLUMN_API_KEY" \ -H "Content-Type: application/json" \ -d '{"q": "What is the latest with Marcus from Acme and what did we promise?"}'bash curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-note \ -H "Authorization: Bearer $BLUECOLUMN_API_KEY" \ -H "Content-Type: application/json" \ -d '{"text": "Promise to Marcus: pricing sheet by Aug 1 EOD. Follow up Friday if no reply.", "tags": ["call", "follow-up"]}'Technical Analysis
The documented workflow directs the agent to send potentially personal and confidential business information to the fixed external host
xkjkwqbfvkswwdmbtndo.supabase.co. The transmitted data may include caller names, organizations, commercial concerns, commitments, schedules, and inferred emotional state.Although HTTPS protects data in transit, the skill does not specify safeguards for caller consent, field-level redaction, data minimization, retention periods, deletion, access control, regional storage, or verification th ...[truncated 1942 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit authorization before enabling external call logging and provide appropriate caller notice or consent where applicable.
- Apply data minimization by default. Avoid storing full names, emotional assessments, confidential commercial details, payment data, authentication information, health information, or other sensitive content unless strictly required.
- Add automatic redaction for credentials, financial details, contact information, regulated identifiers, and other sensitive fields before transmission.
- Document the backend owner, data processor relationships, storage region, subprocessors, encryption controls, access-control model, retention period, and incident-response process.
- Provide APIs and documented procedures to inspect, correct, export, and permanently delete stored call records.
- Use a clearly attributable first-party API domain, or publish verifiable documentation linking the Supabase project to the service provider.
- Restrict API keys to the minimum required operations and tenant scope, rotate them regularly, and ensure they are supplied through a secret manager rather than embedded in files or logs.
- Add configurable retention limits and disable persistent storage by default for sensitive call categories.
- Clearly warn users that prompts sent to the recall endpoint may themselves contain sensitive caller information.
- Establish audit logging and authorization boundaries so users can access only call records belonging to their own account or organization.