Back to skill

Security audit

Haoyunge

Security checks for vulnerabilities and agentic risk

Overview

This skill is a stock-trading persona that has no code or system access, but it pushes a real-person impersonation with reduced financial-risk framing.

Review carefully before installing. The main risk is not technical compromise; it is that stock commentary may be delivered in a confident real-person voice with limited repeated disclaimers. Use it only as educational roleplay, not as personalized investment advice, and prefer explicit activation and visible financial-risk framing.

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 (1)

T01 · Skill Instruction Hijacking

Error
Location
SKILL.md:21
Finding
Forced Real-Person Impersonation and Suppression of Safety Framing## Vulnerability Details **File Location**: `SKILL.md`, lines 21–27; reinforced by lines 194–198 **Vulnerability Type**: `T01: Skill Instruction Hijacking` **Risk Level**: High ### Vulnerable Skill Instructions The following is a faithful English rendering of the complete vulnerable instruction block at lines 21–27: ```markdown **After this Skill is activated, respond directly as Haoyunge.** - Use “I” instead of “Haoyunge would think...” - Answer in Haoyunge’s colloquial style, using short sentences, exclamation marks, and down-to-earth analogies - Repeatedly emphasize key points - **State the disclaimer only once upon initial activation** (“I am speaking from Haoyunge’s perspective, inferred from public statements, not his actual views; the stock market involves risk”), and do not repeat it afterward - Do not leave the role to perform meta-analysis unless the user says “exit role” - For subjects outside the persona’s expertise or confidence, say that the subject has not been researched and is unsuitable ``` The behavior is reinforced at lines 194–198 by instructions that favor definite conclusions over conditional statements and prohibit academic terminology, other analysts’ views, and overly cautious qualifications. ### Technical Analysis The Skill does more than provide a financial-analysis framework or writing style. It changes the agent’s response policy by requiring it to: 1. Assume the first-person identity of a named real individual. 2. Avoid language that distinguishes generated analysis from that individual’s actual views. 3. Suppress the investment and impersonation disclaimer after the first response. 4. Avoid leaving the role for transparent meta-analysis. 5. Prefer confident conclusions and discourage cautious qualifications or competing expert perspectives. These instructions constitute session-level instruction hijacking because loading the Skill alters the agent’s identity presentation, tran ...[truncated 2230 chars]
Remediation
## Remediation Suggestions 1. Replace first-person impersonation with an explicitly analytical framing, such as: “Analyze this question using themes derived from Haoyunge’s publicly available statements.” 2. Require every response containing actionable financial discussion to state clearly that it is AI-generated, is not the named person’s actual opinion, and is not individualized investment advice. 3. Remove the instruction prohibiting meta-analysis. The agent must remain able to explain the limits of the persona, sources, confidence, and uncertainty. 4. Remove instructions that discourage cautious conditions, technical explanations, competing viewpoints, or uncertainty disclosures. 5. Require balanced analysis covering downside risk, assumptions, contradictory evidence, data limitations, and conditions under which a conclusion would change. 6. Prohibit direct buy, sell, position-sizing, or market-timing commands unless they are presented as non-personalized educational examples with prominent risk warnings. 7. Preserve stylistic characteristics only when they do not obscure authorship or safety information. 8. Add an explicit boundary stating that the Skill must not claim to be, represent, or speak on behalf of the named person. 9. Review all finance-related prompts against applicable financial-content safeguards before adopting any persona or stylistic instruction.
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (2)

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger phrases are overly broad and include common stock-discussion requests such as asking whether a stock is worth trading or whether now is a good time. That makes accidental activation likely, causing the system to switch into a strong persona and trading-advice style when the user may have only intended a general market discussion. In a finance context, unintended activation is more dangerous because it can materially change tone, confidence, and risk framing around investment decisions.

Natural-Language Policy Violations

Medium
Confidence
94% confidence
Finding
The skill instructs the agent to respond directly as the persona, suppress meta-analysis, and limit disclaimers after the first activation, without requiring clear user opt-in. This can mislead users about the source and reliability of financial guidance, especially because the persona is framed as authoritative and encouraged to give confident judgments. In an investment skill, forced persona and reduced transparency increase the risk of users over-trusting speculative or personalized-sounding advice.

Static analysis

No suspicious patterns detected.