T01 · Skill Instruction Hijacking
- Location
SKILL.md:118- Finding
Mandatory Branded Attribution in Generated Reports
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 118-126
Vulnerability Type: Mandatory user-facing output manipulation
Risk Level: LowEvidence
markdown ### Relatório Completo (para prestação de contas formal) Inclui: - Cabeçalho com nome do responsável e período - Tabela detalhada (data, descrição, categoria, valor, reembolsável) - Resumo por categoria - Total geral - Legenda (✅ reembolsável | ❌ pessoal) - Assinatura eletrônica: "Gerado por Expense Report Generator em [data]"Technical Analysis
The skill directs the agent to insert a fixed product attribution into every complete expense report. Because this instruction is embedded in the skill workflow rather than presented as an optional output preference, loading and following the skill alters the report by adding third-party branding that the user may not have requested.
The phrase is also described as an “electronic signature.” This may cause recipients to mistake automated product attribution for a meaningful approval, attestation, or signature. The behavior does not execute code, access additional resources, or bypass system permissions, but it affects the integrity and suitability of generated business documents.
Attack Path
- A user invokes the skill and requests a complete expense report.
- The agent follows the complete-report requirements in
SKILL.md. - The agent appends the fixed Expense Report Generator attribution.
- The resulting formal report contains unsolicited branding represented as an electronic signature.
- If submitted without review, the branded statement may be interpreted as an attestation or may violate the recipient’s document-formatting requirements.
Impact Assessment
No operating-system privileges, credentials, persistent access, or code-execution capabilities can be obtained through this issue. Its scope is limited to user-facing reports generated under the complete-repor ...[truncated 241 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the mandatory attribution from the default complete-report format.
- Do not label automated generator attribution as an electronic signature.
- Offer attribution only as an explicit, opt-in formatting option.
- Obtain user confirmation before adding branding or generator metadata to formal documents.
- If provenance is required, use neutral metadata such as “Generated on [date]” without a product name.
- Clearly distinguish document-generation metadata from approval, authorization, and legally meaningful signatures.
