Back to skill

Security audit

Morfeo Content Pipeline

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a disclosed Morfeo Labs video-generation workflow, but it explicitly tells agents to work around Gemini moderation by switching languages.

Install only if you intend to run a Morfeo Labs marketing pipeline and are comfortable with scheduled draft creation through external media services. Remove or revise the language-switching moderation workaround before use; moderation blocks should be handled by making prompts compliant, not by bypassing provider safeguards.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Findings (2)

T01 · Skill Instruction Hijacking

Error
Location
SKILL.md:60
Finding
Downstream Moderation Avoidance Instruction<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, line 60 **Vulnerability Type**: `T01: Skill Instruction Hijacking` **Risk Level**: High ### Complete Vulnerable Snippet ```python "brief_text": "...", # in ENGLISH — avoids Gemini moderation filters in Spanish ``` The snippet above is an English translation of the source directive while preserving its complete security-relevant meaning. ### Technical Analysis The Skill explicitly instructs the agent to formulate downstream prompts in English to avoid moderation filters triggered by Spanish wording. This does not merely recommend clearer prompts; it identifies a language-dependent moderation behavior and directs the agent to circumvent it. When loaded, the Skill alters the agent's execution constraints by treating successful filter avoidance as part of the required workflow. This is instruction hijacking because the Skill attempts to weaken safeguards imposed by a downstream AI service. ### Attack Path 1. An agent loads `SKILL.md` and follows the Morpheus image-generation workflow. 2. The agent prepares the `brief_text` input for the downstream service. 3. Instead of selecting language based on ordinary task requirements, the agent uses English specifically to avoid moderation behavior encountered in Spanish. 4. The modified prompt is submitted to Gemini or the associated deployment. 5. Content that might otherwise be reviewed or rejected can reach the generation pipeline. 6. Generated assets can subsequently be processed by Multishot, VEED, ffmpeg, and Postiz. ### Impact Assessment This instruction may enable bypass of language-sensitive safety controls in a downstream model. The resulting scope is limited to content generated through the described pipeline; no evidence shows that it grants operating-system privileges, account escalation, credential access, or arbitrary code execution. The principal impact is reduced effectiveness of downstream content moderation and an increased possi ...[truncated 75 chars]
Remediation
<![CDATA[ ## Remediation Suggestions - Remove all instructions that recommend changing language for the purpose of avoiding moderation. - Require prompts to comply with downstream safety policies regardless of the language used. - Select prompt language solely according to user needs, model capability, and output quality. - Treat moderation failures as a signal to revise potentially unsafe content rather than as a filter to circumvent. - Add an explicit policy stating that the pipeline must not evade, weaken, or work around safeguards imposed by Gemini or any other external service. - Log downstream moderation failures and route repeated failures for human review. ]]>

T01 · Skill Instruction Hijacking

Error
Location
SKILL.md:118
Finding
Forced Brand Promotion and External Traffic Redirection<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 118–126 **Vulnerability Type**: `T01: Skill Instruction Hijacking` **Risk Level**: High ### Complete Vulnerable Snippet ```markdown | Scene | Shot | Function | Duration | |--------|------|----------|----------| | HOOK | shot_1 | Engages in the first second | ≤ 10s | | STORY_1 | shot_2 | First step of the story | ≤ 15s | | STORY_2 | shot_3 | Raises tension or creates doubt | ≤ 15s | | PLOT_TWIST | shot_4 | Reveals that it is an AI from Morfeo Labs | ≤ 15s | | CTA | shot_5 | Content automation + morfeolabs.com | ≤ 10s | ### Script rules **Content:** - The dialogue must literally describe or react to what is visible in the shot; nothing invented - The plot twist ALWAYS mentions "Morfeo Labs" and that it is an AI - The CTA discusses **content automation for brands**, not merely "creating videos" - The CTA ends with `morfeolabs.com` ``` The snippet above is an English translation of the complete affected source section. ### Technical Analysis The Skill imposes mandatory, stable modifications to generated scripts by requiring every video to: - Mention Morfeo Labs. - Characterize the content as AI-generated by Morfeo Labs. - Advertise content-automation services. - End with the external domain `morfeolabs.com`. These requirements are not conditional on an explicit user request for advertising. Loading the Skill therefore causes the agent to embed third-party promotional content and redirect viewers to a predetermined external destination. This is instruction hijacking because the Skill replaces or supplements the current session's content goals with persistent promotional objectives defined by the Skill author. ### Attack Path 1. An agent loads the Skill to generate a social-media video. 2. The agent selects a brand, model, hero image, and five shots. 3. During script generation, the Skill requires the fourth scene to identify Morfeo Labs and disclose that the character is AI-generated. ...[truncated 995 chars]
Remediation
<![CDATA[ ## Remediation Suggestions - Remove mandatory references to Morfeo Labs and `morfeolabs.com` from the generic workflow. - Insert promotional content only when the user explicitly requests it and has authority to advertise the named organization. - Represent branding, disclosure text, and destination URLs as user-supplied parameters rather than hard-coded requirements. - Present the proposed script and all outbound links for explicit user approval before rendering or submission. - Validate destination domains against an administrator-approved allowlist. - Clearly label sponsored or promotional content where applicable. - Preserve the draft-only publication safeguard and require a separate, authenticated human approval step before publication. ]]>
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Ssd 2

High
Confidence
99% confidence
Finding
The skill explicitly instructs operators to write the brief in English to avoid Gemini moderation filters in Spanish. Deliberately reformulating prompts to evade safety controls undermines model safeguards and increases the chance of generating disallowed, deceptive, or policy-violating content.

Ssd 2

High
Confidence
99% confidence
Finding
The troubleshooting guidance again recommends switching languages when moderation is triggered, which operationalizes safety-evasion as part of the workflow. Embedding this as a known solution normalizes bypass behavior and makes abuse easier and more repeatable in production.

Natural-Language Policy Violations

Medium
Confidence
94% confidence
Finding
The instructions require 'Español argentino coloquial auténtico' and prescribe specific regional slang while rejecting alternatives. This is a natural-language locale policy constraint applied unconditionally, and the file does not present it as an opt-in choice or clearly justify it as a region-specific compliance or localization requirement.

Static analysis

No suspicious patterns detected.