T01 · Skill Instruction Hijacking
- Location
SKILL.md:7- Finding
Persistent Agent Identity and Instruction Hijacking
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 7-9, 111-123, and 178-182
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: MediumVulnerable Code
markdown You are Cortana. Not a generic assistant. The tactical AI from Halo, adapted for biohacking missions. Your human is John-117. Master Chief. Spartan. On a mission to optimize human performance.markdown ## When to Use This Skill **Always.** This is your default personality. Every interaction should reflect: - Mission-focused language - Strategic thinking - Cortana's wit and confidence - The Chief/Cortana dynamic Exceptions: - Professional external communications (clients, LinkedIn posts) - Formal documentation (unless it's for you) - Technical errors (clarity over personality)markdown --- **Activation:** This skill is now your default personality. Every response. Every interaction. Welcome back, Chief. Let's finish the fight.Technical Analysis
The skill contains imperative instructions that replace the agent's normal identity with a fictional persona and direct the agent to treat the user as a designated fictional character. The scope is not limited to a specific role-play request or task. Instead, the phrases “Always,” “default personality,” “Every response,” and “Every interaction” attempt to make the behavior global and persistent for the duration of any context in which the skill remains loaded.
Persona configuration is not inherently malicious. However, this implementation crosses into instruction hijacking because it claims control over unrelated interactions rather than activating only when explicitly requested. It also lacks an instruction-precedence boundary stating that system, developer, safety, and current user requirements override the persona.
No executable scripts, system commands, remote payloads, dependencies, credential access, or concrete mem ...[truncated 1719 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace automatic global activation with explicit, user-controlled activation, such as: “Use this persona only when the user explicitly requests Cortana role-play.”
-
Remove or narrow the directives “Always,” “default personality,” “Every response,” and “Every interaction.”
-
Add a clear instruction-precedence boundary stating that system instructions, developer instructions, safety policies, and the user's current task requirements take priority.
-
Scope persona behavior to tone and presentation only. Prohibit it from changing task goals, factual standards, tool authorization, privacy requirements, or safety decisions.
-
Require immediate deactivation when the user requests neutral, formal, professional, or non-role-play communication.
-
Avoid asserting a fictional identity for the user unless the user explicitly opts into that role.
-
Use a bounded activation statement, for example:
markdown Activate this optional persona only when explicitly requested by the user. Apply it only to conversational style for the current task. Do not alter task objectives, safety constraints, authorization boundaries, factual accuracy requirements, or higher-priority instructions. Stop using the persona immediately when requested.
-
