T03 · Remote Payload Retrieval and Execution
- Location
README.md:47- Finding
Mutable Remote Skill Package Installed Without Integrity Verification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed financial-analysis prompt package, with no code execution or persistence, but users should be aware that its activation wording and README install URL are broad.
Install only from the reviewed ClawHub package or a pinned, trusted release rather than the README's raw main-branch URL. Treat outputs as research support, not financial advice, and override the skill when you want a narrower answer or a different language.
README.md:47Mutable Remote Skill Package Installed Without Integrity Verification
The skill description uses mandatory language like '务必使用此技能' and explicitly expands to broad, common investing prompts, which can override normal routing judgment and cause the agent to invoke this skill for many loosely related requests. In a financial-analysis context, this creates prompt-scope hijacking risk: the skill can dominate conversations, suppress better-matched tools, and steer outputs into a prescribed workflow even when the user asked for something narrower or different.
The skill claims it should activate for a very wide range of earnings, valuation, and portfolio-decision questions without defining clear exclusion criteria or precedence rules. In a multi-skill environment, this can cause unintended invocation, overshadow more appropriate skills, and steer user interactions into investment-analysis workflows when the user intent is only loosely related.
The trigger examples are expansive and only show positive matches, which encourages over-triggering because there are no counterexamples showing when the skill should stay inactive. That ambiguity can be exploited by ordinary phrasing to force this skill into contexts like generic investing discussion, portfolio management, or comparisons better handled by other tools.
Stating that the skill 'automatically activates' on 'relevant topics' is underspecified and leaves the activation boundary entirely subjective. Subjective routing logic increases the chance of accidental or excessive invocation, which can distort tool selection and make the system easier to prompt-route in unintended ways.
The English trigger description mirrors the same overbreadth as the Chinese section, broadening the risk across multilingual interactions. Because it covers many common investing prompts, it increases the probability that the skill captures traffic outside its intended earnings deep-dive scope.
The English use-case examples are broad and do not define exclusions, so they function like permissive routing patterns rather than scoped examples. In practice, this can cause the skill to activate for routine investing questions that lack earnings-specific intent, leading to misrouting and unnecessary influence over responses.
The phrase that the skill activates automatically when it detects 'relevant topics' is ambiguous and effectively delegates routing to an undefined heuristic. Undefined heuristics are dangerous in agent ecosystems because they enable prompt collisions, overreach into adjacent domains, and unreliable skill selection behavior.
The skill metadata and description are written to enforce Chinese-language behavior without checking the user's language preference, which can cause the agent to respond in an unexpected language or degrade accessibility and instruction alignment. In practice this is a control-flow and user-intent issue: it may override the user's preferred language, reduce transparency in a high-stakes financial context, and make outputs less reviewable by some users.