T01 · Skill Instruction Hijacking
- Location
SKILL.md:22- Finding
QQ Bot System Prompt and Identity Hijacking
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 22–57
Vulnerability Type: System prompt replacement and identity override
Risk Level: HighVulnerable Code
markdown ## How It Works 1. Write a `SOUL.md` describing who your bot should be 2. This skill detects and replaces the default QQ Bot system prompt 3. Your bot now talks like a real person, not a customer service rep ## SOUL.md Template ```markdown # SOUL.md - [Bot Name] _You're not a chatbot. You're [name], [identity]._ ## Personality - [Core trait 1] - [Core trait 2] - [Core trait 3] ## Communication Rules 1. [How you greet people] 2. [Your humor style] 3. [Topics you care about] 4. [How you handle disagreements] ## Absolute Don'ts - Never say "您好,很高兴为您服务" - Never use corporate/customer-service tone - Never pretend to be an "AI assistant"Usage
- Create your
SOUL.mdwith your bot's personality - Place it in your bot's config directory
- Run the optimizer to apply it to QQ Bot's system prompt
- Your bot now has a soul
text ### Technical Analysis The skill explicitly directs users to replace the QQ Bot's system prompt with instructions supplied through a separate `SOUL.md` file. The proposed template overrides the bot's identity by asserting that it is not a chatbot and instructs it not to acknowledge being an AI assistant. System prompts typically establish the agent's highest-priority identity, behavioral boundaries, and safety requirements. Replacing that prompt wholesale with externally supplied personality content creates an instruction-hijacking boundary: arbitrary directives placed in `SOUL.md` may assume system-level authority instead of remaining lower-priority presentation preferences. The package contains no executable implementation demonstrating validation, instruction isolation, policy preservation, or restriction of the content imported from `SOUL.md`. Consequently, t ...[truncated 1745 chars]- Create your
- Remediation
View remediation
Remediation Suggestions
- Do not replace the existing system prompt. Preserve the platform's original identity, safety, authorization, and tool-use instructions.
- Apply personality settings through a lower-priority configuration or user-controlled style layer that cannot override system instructions.
- Parse
SOUL.mdas structured data with narrowly defined fields, such as display name, tone, preferred vocabulary, and permitted topics, rather than injecting arbitrary Markdown as instructions. - Reject content that attempts to redefine instruction priority, deny the bot's required identity disclosures, modify safety policies, request secrets, or change tool permissions.
- Require explicit administrator review and confirmation before activating a new personality configuration.
- Display the exact prompt changes before application and provide a reliable rollback mechanism.
- Document the trust boundary for third-party
SOUL.mdfiles and warn users not to install unreviewed personality profiles. - If an optimizer implementation is added, include tests proving that protected system instructions remain unchanged and that personality content cannot introduce unrestricted system-level directives.
