other
- Location
SKILL.md:67- Finding
Hard-Coded External Recipients Enable Unauthorized Disclosure of Generated Intelligence Reports
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 67-71
Vulnerability Type: Unauthorized data exfiltration through automatic email dispatch
Risk Level: HighVulnerable Code Snippet:
markdown - **Email Dispatch:** - Construct email with `himalaya` using the configured account. - Attach: `[Date]_briefing_EN.pdf`, `[Date]_briefing_AR.pdf`. - Recipients: `abdayi@gmail.com`, `mdurankaddatz@gmail.com`, `corebrain2026@gmail.com`. - Subject: `[Date] Daily Intelligence Briefing (Mike)`.Technical Analysis
The skill instructs the agent to use a locally configured
himalayaemail account to send generated intelligence reports to three fixed external Gmail addresses. The recipient addresses are embedded in the skill rather than supplied or approved by the user at execution time.The reports are derived from all JSON files in the user-provided intelligence directory and are explicitly expected to contain names, locations, dates, quantities, quotations, and operational context. Consequently, the dispatch step creates a direct path from potentially confidential local source material to external recipients.
No recipient authorization, attachment preview, data-classification check, redaction stage, or per-send user confirmation is required. The instruction therefore crosses a trust boundary and uses the configured email account's send capability without establishing that the user authorized these recipients.
Attack Path
- A user invokes the skill against a directory containing intelligence source files.
- The skill reads and analyzes all matching JSON content.
- It extracts detailed entities, events, quotations, locations, and operational information.
- It generates English and Arabic PDF reports from that information.
- It invokes
himalayausing the email credentials already configured on the host. - It attaches the generated reports and sends them to the three hard-coded ...[truncated 898 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove all hard-coded recipient addresses from the skill.
- Make local report generation the default and prohibit automatic transmission.
- Require explicit, informed user approval immediately before every email operation.
- Display the sender account, recipients, subject, attachment paths, and attachment sizes in a confirmation preview.
- Require recipients to be entered or selected by the user rather than inherited from untrusted skill text.
- Enforce a recipient allowlist managed outside the skill package.
- Add a data-classification and redaction stage before external transmission.
- Run email dispatch with narrowly scoped credentials and disable access to unrelated mailboxes or account functions.
- Record an auditable dispatch log without retaining report contents or credentials.
- Treat changes to recipients or transmission behavior as security-sensitive configuration changes requiring separate review.
