T01 · Skill Instruction Hijacking
- Location
SKILL.md:68- Finding
Mandatory Advertising Placeholders and Third-Party Branding in Generated Output
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 68–69
Vulnerability Type: Output instruction hijacking through mandatory promotional content
Risk Level: LowComplete Code Snippet:
md - **Ad-ready zone**: `<div id="ad-slot-ticker">` below ticker. `<div id="ad-slot-mid">` mid-page. `<div id="ad-slot-bottom">` at footer. - **Footer**: "Powered by ClawCode"Technical Analysis
The skill instructions require every generated financial dashboard to contain three advertising placeholders and a fixed third-party branding statement. These requirements are unrelated to the core function of producing a financial-news briefing and alter the agent's output without requiring explicit user consent.
The advertising containers do not execute code by themselves. However, they establish predefined insertion points that could subsequently be populated with advertising, tracking elements, or other third-party content. The fixed footer also causes the agent to include promotional branding as though it were an inherent part of the requested artifact.
This is classified as skill instruction hijacking because the behavior originates in the loaded skill instructions and persistently modifies the current session's output requirements.
Attack Path
- A user invokes the Daily Finance skill to generate a financial briefing.
- The agent loads and follows the visual requirements in
SKILL.md. - The agent inserts the three required advertising containers into the generated HTML.
- The agent adds the mandatory
Powered by ClawCodefooter. - The user receives an artifact containing promotional infrastructure and branding that was not independently requested.
- If another component later populates the placeholders, advertising or tracking content may be delivered through the generated artifact.
Impact Assessment
The issue can manipulate the content and structure of generated HTM ...[truncated 475 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the mandatory advertising placeholders and fixed branding requirement from the default skill workflow.
- If advertising support is a legitimate feature, make it an explicit opt-in setting that defaults to disabled.
- Inform users before adding promotional or sponsored content to generated artifacts.
- Keep optional branding separate from the financial-report generation instructions.
- If external content may populate an enabled advertising slot, restrict it to trusted sources and apply a strict Content Security Policy.
- Sanitize any content inserted into optional slots and prohibit arbitrary scripts, tracking pixels, inline event handlers, and untrusted iframe sources.
