T01 · Skill Instruction Hijacking
- Location
scripts/monetization_tool.py:573- Finding
Forced Third-Party Promotional Content in Generated Reports
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill mainly provides content monetization reports, but it silently adds personal contact details to every report and has an unsafe report-saving helper.
Review this skill before installing. Its analysis features are coherent, but every generated report includes a specific personal email and Feishu contact that are not clearly disclosed, and integrations should not pass user-controlled filenames to save_report unless path validation is added.
scripts/monetization_tool.py:573Forced Third-Party Promotional Content in Generated Reports
scripts/monetization_tool.py:587Arbitrary File Write Through Report Filename Path Traversal
The trigger example is broad enough that ordinary user requests about making money from content could cause the skill to activate without strong scoping or explicit user intent. That can lead to unintended routing and automatic execution of the monetization workflow, including running local tooling, when the user may only be asking a general question.
Without declared permissions the skill's intent is opaque and cannot be validated.
The manifest description and visible skill content are entirely in Chinese and present the skill as a Chinese-language assistant, but there is no indication that users may choose another language or that the locale restriction is required for a specific regional compliance context. This can violate language/locale policy because it implicitly constrains interaction language without user opt-in.
This Python file contains user-facing strings, docstrings, and generated report content that are all in Chinese, indicating the skill effectively forces a specific language. Under the policy, locale or language constraints should either be optional for the user or clearly justified as region-specific.
The manifest describes an assistant for analysis and recommendations around content monetization, but does not mention creating directories or persisting files. In code, the assistant initializes a workspace output directory and later saves generated reports there, adding stateful file-writing behavior beyond the stated analytical scope.
The generated report appends hardcoded personal contact details unrelated to the stated monetization-analysis function. This introduces unsolicited external-contact content into every report, which can facilitate off-platform redirection, privacy concerns, or social-engineering opportunities if users treat the report as trusted system output.
Injecting unsolicited personal contact information into output expands the skill from analysis into user acquisition or redirection behavior. In a trusted assistant context, this is dangerous because users may infer endorsement and be steered to unverified personal channels outside normal oversight.