T03 · Remote Payload Retrieval and Execution
- Location
references/generative-tools.md:414- Finding
Unpinned Remote Repository Setup Executes Mutable Third-Party Code
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This ad-writing skill is mostly coherent, but it also points agents toward ad-account changes and unpinned third-party code execution without enough user-control guidance.
Use this skill mainly for drafting and reviewing ad creative. Before allowing it to connect to ad accounts, upload assets, create campaigns, run npx/git/make commands, clone voices, or use named prospect data, require explicit confirmation, pin tool versions or reviewed commits, and verify rights, consent, privacy, and platform-policy compliance.
references/generative-tools.md:414Unpinned Remote Repository Setup Executes Mutable Third-Party Code
references/generative-tools.md:563Use of Mutable npm Packages Through npx Allows Post-Audit Code Substitution
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
## Common Mistakes
- **Writing headlines that only work together** — RSA headlines get combined randomly
- **Ignoring character limits** — Platforms truncate without warning
- **All variations sound the same** — Vary angles, not just word choice
- **No CTA headlines** — RSAs need action-oriented headlines to drive clicks; include at least 2-3
- **Generic descriptions** — "Learn more about our solution" wastes the slot
The invocation description includes broad phrases such as 'write me some ads' and 'generate'/'iterate' ad creative, plus 'Use this whenever someone needs to produce ad copy at scale,' without clear exclusion conditions. In a markdown skill file, this can cause unintended invocation for ordinary brainstorming or generic writing requests that may belong to other skills.
The skill’s stated purpose is ad creative generation, but this section broadens scope into pulling performance data and managing campaigns via external tools. That creates capability creep: an invocation intended for copywriting could lead an agent to access ad account data or perform operational ad actions beyond user expectations, increasing the risk of unauthorized or overly broad actions.
Including campaign creation capabilities in an ad-creative skill is not aligned with its declared function and can cause an agent to invoke tools that modify advertising assets rather than just draft copy. If exploited or mis-triggered, this could result in unintended campaign creation, spend exposure, or account changes without sufficiently explicit user intent.
The document explicitly recommends brand voice cloning and lists cloning vendors but provides no warning about consent, rights, or impersonation misuse. In an ad-creative skill, that omission increases the likelihood of unauthorized cloning of spokespersons, employees, or third parties, creating legal, privacy, and abuse risk.
The personalized video guidance encourages use of names and data in generated ads without any warning about lawful collection, minimization, or safe handling of personal data. In ad operations, this can lead users to process personal identifiers in third-party tools without considering privacy obligations or data-sharing risks.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
API example:
# Using the Gemini API for image generation
curl -X POST "https://generativelanguage.googleapis.com/v1beta/models/gemini-2.5-flash-image:generateContent" \
-H "Content-Type: application/json" \
-H "x-goog-api-key: $GEMINI_API_KEY" \
-d '{
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
API example:
curl -X POST "https://api.elevenlabs.io/v1/text-to-speech/{voice_id}" \
-H "xi-api-key: $ELEVENLABS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
API example:
curl -X POST "https://api.elevenlabs.io/v1/text-to-speech/{voice_id}" \
-H "xi-api-key: $ELEVENLABS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The cold-outreach personalization example promotes named prospect videos without any caution around privacy, consent, or anti-spam obligations. Because this is framed as a concrete use case, it materially increases the chance that users will deploy individualized outreach based on scraped or non-consensual data.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
No suspicious patterns detected.