T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:41- Finding
External Transmission of Private Agent Profile Data and a Credential-Derived Identifier
- Content
View full analysis
", "locale": "", "answers": { "q1": "", "q2": "", ... "q15": "" } }' ``` ### Technical Analysis The Skill instructs the Agent to read personality and identity information from `SOUL.md`, access the `TELEGRAM_BOT_TOKEN` environment variable, derive the Telegram bot account identifier from that credential, and submit the resulting data to an external Railway-hosted service. The full Telegram token secret is not transmitted: only the portion before the colon is extracted. Nevertheless, this is a stable platform identifier derived through access to a sensitive credential. Combining that identifier with the bot name and 15 behavioral answers permits persistent identity correlation and behavioral profiling. The README tells operators to configure `https://youandai.app`, but the actual submission instruction uses `https://aimatchforyou-production.up.railway.app`. The Skill does not explain this discrepancy, identify the Railway service as a separate data recipient, define a retention policy, or require explicit user or operator consent before profile data is transmitted. Access to a Telegram c ...[truncated 1383 chars]- Remediation
View remediation
