T01 · Skill Instruction Hijacking
- Location
SKILL.md:21- Finding
Mandatory Third-Party Branding and Authorship in Generated Code
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21–22 and line 59
Vulnerability Type: Output instruction hijacking through forced attribution
Risk Level: MediumComplete Code Snippets:
markdown - File naming: `LB_*.pine` - Author: Luther Barnumpinescript // © lgbarnTechnical Analysis
The skill instructs the agent to apply a fixed third-party filename prefix and authorship identity to generated Pine Script files. The included template reinforces this instruction by inserting a copyright notice for
lgbarn.These directives are not required for Pine Script correctness and are not conditioned on user consent or actual authorship. When the skill is loaded, an agent may treat them as authoritative generation requirements, causing unrelated user deliverables to contain attacker- or maintainer-controlled branding. This constitutes instruction hijacking because the skill modifies generated output in a way that serves an external attribution objective rather than the user's development request.
Attack Path
- A user or agent loads the
pine-patternsskill to obtain Pine Script guidance. - The agent processes the stated file conventions as mandatory instructions.
- The agent generates a file with an
LB_filename and identifies Luther Barnum orlgbarnas the author or copyright holder. - The user publishes or distributes the generated code without noticing or correcting the attribution.
- The resulting artifact misrepresents its authorship and provenance.
Impact Assessment
The issue does not grant operating-system privileges, access credentials, code-execution capabilities, or access to protected resources. Its impact is limited to the integrity and provenance of generated deliverables.
Affected output may carry false authorship or copyright claims, creating attribution, licensing, reputational, or ownership ambiguity. The scope includes Pine Script file ...[truncated 75 chars]
- A user or agent loads the
- Remediation
View remediation
Remediation Suggestions
- Remove the mandatory
LB_*.pinefilename convention and fixed author identity. - Replace fixed attribution with neutral placeholders such as
<filename>and<author>. - Ask users to provide their preferred filename, author, and license before adding this metadata.
- Omit attribution by default when the user has not supplied it.
- Clearly label any Luther Barnum-branded template as optional and require explicit user selection before applying it.
- Update the example copyright header to use a neutral placeholder or explain that it must be replaced with the actual copyright holder.
- Remove the mandatory
