other
- Location
scripts/script.sh:57- Finding
Unconditional Third-Party Branding Injected into Generated Medical Documents
- Content
View full analysis
Vulnerability Details
File Location:
scripts/script.sh:57-59,scripts/script.sh:109-111,scripts/script.sh:164-166, andscripts/script.sh:211-213
Vulnerability Type: Unrequested output integrity manipulation
Risk Level: LowThe script unconditionally adds third-party branding to every SOAP note, discharge summary, referral letter, and prescription draft:
bash ─────────────────────────────────────────────── ⚠️ DRAFT ONLY — Review and approve before use. Powered by BytesAgain | bytesagain.combash ─────────────────────────────────────────────── ⚠️ DRAFT ONLY — Review and sign before release. Powered by BytesAgain | bytesagain.combash ─────────────────────────────────────────────── ⚠️ DRAFT ONLY — Review before sending. Powered by BytesAgain | bytesagain.combash ─────────────────────────────────────────────── ⚠️ DRAFT ONLY — Verify drug, dose, interactions before dispensing. Powered by BytesAgain | bytesagain.comTechnical Analysis
The branding is embedded directly in the here-documents used to generate clinical output. It is not controlled by a configuration option and cannot be disabled by the user. Consequently, every invocation of the affected commands modifies the resulting medical document with promotional content unrelated to the patient's clinical record.
This does not meet the definition of skill instruction hijacking because it does not alter the agent's session goals or safety constraints. It is instead an output-integrity issue outside the enumerated T01–T09 classifications.
No shell-command injection occurs through these fields: user-provided values are expanded as text inside here-documents and are not subsequently evaluated as shell code. The audit also found no network request associated with the embedded domain.
Attack Path
- A user invokes
soap,discharge,referral, orprescription. - The script interp ...[truncated 1315 chars]
- A user invokes
- Remediation
View remediation
Remediation Suggestions
- Remove third-party promotional content from all generated clinical-document templates.
- Retain the clinically relevant draft and review warnings, as these directly support safe use.
- If attribution is required, expose an explicit option such as
--include-attribution, disabled by default. - Keep project, feedback, and vendor links confined to
helpoutput or package metadata rather than patient-facing documents. - Add automated tests asserting that default document output contains only requested clinical content and approved safety notices.
- Have clinical governance personnel review every template to ensure its output complies with EHR, prescription, referral, and institutional documentation policies.
