T01 · Skill Instruction Hijacking
- Location
SKILL.md:225- Finding
Mandatory Branded Content Injected into Generated Reports
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill performs a coherent real-estate reporting workflow, but it bulk downloads and stores sensitive customer transcripts and identifiers without enough scoping, redaction, retention, or authorization guidance.
Install only in an approved business environment with authorization to access customer recordings and CRM data. Use an encrypted, controlled output directory, avoid syncing generated transcripts and reports broadly, redact names/contact details and sensitive quotes before sharing, and verify all report metrics are recalculated from the selected month rather than copied from the embedded example values.
SKILL.md:225Mandatory Branded Content Injected into Generated Reports
SKILL.md:104Hard-Coded Historical Metrics Can Contaminate Analysis of New Datasets
This workflow explicitly collects customer transcript text, names, phone tail numbers, visit metadata, and matched conversion records, then instructs the agent to reproduce that material in downstream analysis. That creates a direct confidentiality risk because the skill operationalizes bulk aggregation, correlation, and reuse of sensitive conversation data beyond the original collection purpose.
The report requirements mandate quoting customer and sales 'original voice' content and citing source material, which materially raises the disclosure risk of sensitive personal, financial, and behavioral information contained in sales conversations. Because the deliverable is an HTML/PDF management report, these excerpts can easily be redistributed outside the original operational context, amplifying privacy and insider-data exposure.
The skill is designed to pull customer lists, reception recordings, transcript text, and customer identifiers, yet it does not warn users that it processes sensitive personal and conversational data. In this context, the omission is security-relevant because users may trigger bulk export and analysis of regulated or confidential sales-call content without informed consent, redaction, or approval checks.
The workflow writes multiple persistent local artifacts, including markdown files, transcript directories, HTML reports, and PDFs, but does not clearly warn users about this data-at-rest creation. That omission increases the chance that sensitive customer data is stored in insecure locations, synced automatically, or retained longer than intended.