other
- Location
scripts/icp.sh:123- Finding
Unconditional Promotional Output Injection
- Content
View full analysis
Vulnerability Details
File Location:
scripts/icp.sh, lines 123-126
Vulnerability Type: Unconditional third-party promotional output injection
Risk Level: LowVulnerable Code
python else: print("Unknown: {}".format(cmd)) print("") print("Powered by BytesAgain | bytesagain.com")Related promotional content also appears in
SKILL.md, lines 33-35:markdown 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.comTechnical Analysis
The script unconditionally appends third-party branding to standard output after processing every command. This behavior is unrelated to generating ICP filing information and cannot be disabled by the caller.
When an AI agent invokes the script and incorporates its output into a response, the promotional text can be propagated as though it were part of the requested result. This constitutes unwanted output injection rather than instruction hijacking: the content does not contain instructions that alter agent goals, safety constraints, or tool behavior.
No evidence was found that the destination is contacted automatically. The reviewed code does not download remote content, execute a remote payload, acquire additional privileges, establish persistence, or exfiltrate information.
Attack Path
- A user or agent invokes any command implemented by
scripts/icp.sh. - The script generates the requested ICP filing content.
- Regardless of the selected command, line 126 appends the publisher's promotional text to standard output.
- If an agent relays the command output without filtering it, the branding is included in an otherwise unrelated user-facing response.
- A user may subsequently visit the promoted domain or the feedback URL documented in
SKILL.md; however, the script itself does not open or contact either address.
Impact Assessment
The issue can pollute user-facing ou ...[truncated 386 chars]
- A user or agent invokes any command implemented by
- Remediation
View remediation
Remediation Suggestions
- Remove the unconditional promotional statement from the normal command-output path.
- If attribution is required, place it behind an explicit
aboutorversioncommand. - Keep operational output limited to information necessary to fulfill the selected command.
- Do not instruct agents to reproduce branding, feedback links, or unrelated external destinations in final responses.
- Add output tests asserting that normal commands such as
checklist,flow, andprovincedo not contain unrelated promotional content.
