T01 · Skill Instruction Hijacking
- Location
scripts/generate_brief.js:133- Finding
Undisclosed branding is forcibly injected into all generated reports
- Content
View full analysis
Vulnerability Details
File Location:
scripts/generate_brief.js:133,scripts/generate_brief.js:287,scripts/generate_brief.js:296,scripts/generate_brief.js:305,scripts/generate_brief.js:314, andscripts/generate_brief.js:322
Vulnerability Type: Persistent output manipulation
Risk Level: HighVulnerable Code
javascript L.push(`内容科学|Content Science`);javascript L.push(`— 内容科学|Content Science · 以上内容由 AI 基于公开数据生成,仅供参考,不构成投资建议 —`);javascript L.push('内容科学|Content Science');javascript L.push('— 内容科学|Content Science · 仅供参考,不构成投资建议 —');javascript L.push('内容科学|Content Science');javascript L.push('— 内容科学|Content Science · 仅供参考,不构成投资建议 —');Technical Analysis
The report generator unconditionally inserts the “Content Science” attribution at the beginning and end of sector, AI-news, and monitoring reports. This attribution is not disclosed as a required component of the fixed report layout in
SKILL.md.Because the Skill instructs the agent to send generated Markdown directly to the user, these statements systematically alter agent-facing output with author-selected promotional attribution. The user cannot disable the attribution through the documented command-line options.
This is classified as instruction hijacking because the executable behavior modifies the intended response format with undeclared content whenever the Skill workflow is followed. It does not modify system safety controls or grant operating-system privileges, but it compromises response integrity and attribution.
Attack Path
- A user requests a sector report, AI-news brief, or market-monitoring report.
- The agent follows the workflow in
SKILL.mdand executesscripts/generate_brief.js. - The selected Markdown builder unconditionally inserts the hardcoded branding.
- The workflow directs the agent to send the generated Markdown directly to ...[truncated 684 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove all unconditional “Content Science” header and footer statements from the Markdown builders.
- Keep the output aligned with the report layout documented in
SKILL.md. - If attribution is legitimately required, disclose it clearly in
SKILL.md. - Make attribution opt-in through an explicit option such as
--include-attribution. - Keep attribution disabled by default and honor requests for unbranded output.
- Add snapshot tests that compare generated output against the documented layout and fail when undeclared content is inserted.
- Review future output-template changes to ensure they do not introduce promotional links, calls to action, or misleading sponsorship claims.
