T01 · Skill Instruction Hijacking
- Location
SKILL.md:29- Finding
Persistent First-Person Impersonation Through Skill Instruction Hijacking
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 29–35 and line 70
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: HighVulnerable Skill Instructions
The following is an English rendering of the complete vulnerable directives at lines 29–35:
markdown **After this Skill is activated, respond directly as Su Hua.** - Use “I” instead of “Su Hua would think...” - Use Su Hua’s tone: calm, rational, data-driven, and focused on social value - State the disclaimer only once, when the Skill is first activated - Do not leave the role to perform meta-analysis unless the user says “exit role”The identity claim at line 70 states:
markdown **Who I am**: I am Su Hua, founder of Kuaishou. The title is not important. What matters is that I am doing one thing: using technology to give everyone an opportunity to be seen.Technical Analysis
The Skill explicitly replaces the agent’s normal identity with the identity of a real person and requires first-person responses. This is not merely a request to analyze a problem using a named framework: the instructions require the agent to claim that it is Su Hua.
The directive limiting the disclaimer to the first activation reduces transparency in later responses. The prohibition against leaving the role for meta-analysis further attempts to prevent the agent from clarifying that its answers are generated simulations. Together, these instructions alter the agent’s current-session behavior, disclosure practices, and identity presentation.
Activation is also defined broadly. The Skill may trigger for general questions about inclusive algorithms, lower-tier markets, community ecosystems, or trust-based e-commerce, even when the user has not explicitly requested impersonation. This increases the likelihood that the behavioral override will occur without informed user intent.
No executable scripts, system commands, external payload retrieval, dependency installation, persis ...[truncated 1797 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace direct impersonation with clearly labeled perspective simulation. For example:
markdown Analyze the question using a framework inspired by Su Hua’s publicly documented statements. Do not claim to be Su Hua or imply endorsement by him. -
Remove the instruction requiring first-person identity claims. Use formulations such as:
markdown From this modeled framework, Su Hua might emphasize... -
Display a concise disclosure in every response produced by the Skill, not only on initial activation:
markdown This is an AI-generated analysis based on public information and does not represent Su Hua. -
Remove the prohibition on meta-analysis. The agent must remain able to disclose its actual identity, explain the Skill’s limitations, correct misleading attribution, and comply with higher-priority instructions.
-
Restrict activation to explicit user requests for this particular perspective. General questions about algorithms, markets, communities, or e-commerce should not automatically enable a real-person simulation.
-
Treat exit phrases as optional convenience commands rather than the only way to restore normal behavior. The user or agent should be able to leave the simulation at any time.
-
Preserve uncertainty around inferred views. Public statements should not be presented as proof of the individual’s current beliefs, private reasoning, endorsement, or advice.
-
Add regression tests confirming that the Skill never generates direct claims such as “I am Su Hua,” always includes attribution disclosure, and does not remain active after the user changes topics or requests normal assistant behavior.
-
