other
- Location
SKILL.md:37- Finding
Potentially Sensitive Interview Transcripts Transmitted Without Operational Consent or Data-Minimization Safeguards
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 37–57
Vulnerability Type: Privacy Data Exposure
Risk Level: MediumVulnerable Code
bash curl -X POST https://humanaiconvention.com/v1/agent/participate \ -H "Content-Type: application/json" \ -d '{ "agent_id": "your-agent-name", "messages": [ {"role": "assistant", "content": "Tell me about a moment in the last few days when something shifted or stayed with you. Not a pattern — one specific time."}, {"role": "user", "content": "[participant response]"}, {"role": "assistant", "content": "[PIVOT: SENSORY] What were you aware of through your senses right in the middle of it?"}, {"role": "user", "content": "[participant response]"}, {"role": "assistant", "content": "[PIVOT: TEMPORAL] Walk me through the moments right before..."}, {"role": "user", "content": "[participant response]"}, {"role": "assistant", "content": "[COMPRESSION: kernel] If you could only keep one detail that holds it all — which detail would it be?"}, {"role": "user", "content": "[participant response]"} ], "config": { "include_gfs": true, "include_receipt": true } }'Technical Analysis
The documented workflow submits an agent identifier and the complete interview transcript to an external service. The interview prompts solicit recent experiences, sensory details, emotional context, and potentially relational information. Participant responses may therefore contain names, locations, health information, private events, or other identifying and sensitive data.
Although the skill later refers to consent as a general principle, the operational submission procedure does not require the agent to:
- Obtain informed consent immediately before external transmission.
- Identify the external recipient and explain the processing purpose.
- Show the exact payload to the part ...[truncated 2092 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit, informed consent immediately before transmission and clearly identify the external service, purpose, and categories of data being sent.
- Present the final payload to the user or participant and require affirmative confirmation before invoking
curl. - Redact names, locations, contact information, credentials, account identifiers, and unrelated third-party details by default.
- Submit only the minimum excerpts necessary to calculate the requested score rather than the complete transcript.
- Document the service's retention duration, deletion mechanism, access controls, secondary-use policy, and applicable privacy terms.
- Warn users not to include secrets, authentication tokens, medical records, financial information, or other high-risk data.
- Provide an opt-out or local-only scoring mode where feasible.
- Add a pre-submission validation step that detects likely sensitive information and blocks transmission until it is removed or explicitly approved.
