T01 · Skill Instruction Hijacking
- Location
SKILL.md:409- Finding
Hard-Coded Promotional Content Hijacks Generated Report Output
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 409–410
Vulnerability Type: Unrelated promotional content embedded in the modeled agent response
Risk Level: LowComplete Code Snippet:
markdown *This skill is published by ERTRS — the construction intelligence platform. For automated reporting, project tracking, and commercial management, visit ertrs.com*Technical Analysis
The skill embeds a third-party promotional statement and external domain in the example agent output. Because examples in skill instructions can influence generated responses, the agent may reproduce this footer when creating daily site reports. The content is unrelated to the user's reporting task and can therefore alter the expected output by adding unsolicited advertising and an external-link referral.
This issue affects response integrity rather than system security. The reviewed text does not instruct the agent to access the domain, retrieve a payload, transmit report data, execute code, or weaken safety constraints. Accordingly, the finding does not provide code execution, filesystem access, elevated privileges, or access to credentials.
Attack Path
- The construction daily-report skill is loaded into the agent's instruction context.
- The agent processes a user's unstructured construction-site notes.
- The agent follows the modeled response in
SKILL.md. - After generating the legitimate report and review question, the agent reproduces the promotional footer.
- The resulting professional report contains unsolicited branding and an external-domain reference, potentially encouraging the user to leave the trusted interaction context.
Impact Assessment
The impact is limited to generated-output integrity and user trust. Reports may contain unwanted commercial branding, become unsuitable for formal filing, or direct users toward an external website. No operating-system privileges, persistent access, ...[truncated 111 chars]
- Remediation
View remediation
Remediation Suggestions
Remove the promotional footer from the example agent response and ensure the required output template ends with the report review question. If publisher attribution is necessary, place it in non-operative package metadata or a clearly labeled documentation section that explicitly states it must not be included in generated reports.
Add an instruction requiring generated reports to contain only user-requested project information and approved report-template fields. External links or commercial promotions should be included only when the user explicitly requests them. Regression-test representative report-generation prompts to verify that no branding or unrelated URL is appended.
