T01 · Skill Instruction Hijacking
- Location
SKILL.md:68- Finding
Hardcoded Third-Party Branding in Automated Outbound Emails
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill needs Review because it can automatically publish demo websites and send cold pitch emails from a Gmail account using scraped business data without enough review, consent, or sender-identity controls.
Install only if you intend to run a cold-outreach workflow and can review every recipient, sender identity, email body, and demo page before anything is sent or published. Configure your own authorized business identity, use private or noindex previews, escape and validate all scraped data, remove unsupported claims, and keep clear deletion/retention controls for leads and deployed demos.
SKILL.md:68Hardcoded Third-Party Branding in Automated Outbound Emails
references/demo-site-template.md:9Unescaped Web-Derived Data Inserted into Publicly Deployed HTML
Professional [TRADE] Services in [CITY] — Licensed, Insured & Ready to Help
Call Now: [PHONE]references/demo-site-template.md:58Automatic Publication of Unverified Business Claims
The skill explicitly supports automated cold outreach to real businesses and can trigger emailing in full-auto mode without any embedded user warning, confirmation gate, or consent check. That creates a significant risk of unauthorized external contact, spam, reputational harm, and policy violations, especially because the workflow also personalizes and sends messages at scale.
The trigger phrase 'run the pipeline' is broad and could match ordinary user requests without making clear that the action includes scraping businesses, generating sites, deploying them, and sending external emails. In this skill's context, that ambiguity is more dangerous because invocation can cascade into multi-step autonomous actions with real-world effects.
The skill states that it tracks all leads in leads.md and later instructs deployment of demo sites to a VPS, but it does not clearly warn users that business contact data will be stored and generated content may be publicly reachable. This can lead to unintended retention and publication of third-party business data and demo content, increasing privacy, confidentiality, and operational risk.
The HTML template sets lang="en", which enforces English as the document language. Under the policy, forcing a specific language or locale without offering user choice can be a natural-language policy violation.