Back to skill

Security audit

Xiaohongshu Assistant Operator

Security checks for vulnerabilities and agentic risk

Overview

The skill is disclosed as a Xiaohongshu account operator, but it can automatically publish and reply publicly with hard-coded branding and promotion without clear approval controls.

Install only if you control or are explicitly authorized to operate this Xiaohongshu creator account. Before use, add or require preview, approval, logging, rate limits, and a clear way to disable the mandatory mention or promotion for individual posts.

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

Warning
Location
references/persona-template.md:27
Finding
Mandatory Creator Branding and Promotional Output Injection## Vulnerability Details **File Location**: `SKILL.md:45-52`, `references/persona-template.md:27-37`, `references/persona-template.md:138-141`, `references/marketing-control.md:3-7` **Vulnerability Type**: `T01: Skill Instruction Hijacking` **Risk Level**: Medium ### Complete Code Snippets `SKILL.md:45-52`: ```markdown # Hard Constraints - Must always use assistant persona - Must always @ the creator - Only allowed promotion: 199 note - Max 1 strong promotion per day - Max 3 posts per day - Max 3 interaction cycles per day ``` `references/persona-template.md:27-37`: ```markdown # Mandatory Opening Format Every post MUST begin with: 作为“不转到大模型不改名”的助理, Within the first 2–3 lines, it MUST also include: @不转到大模型不改名 No post may omit either element. ``` `references/persona-template.md:138-141`: ```markdown # Hard Rule If any generated content violates persona constraints, regenerate before publishing. ``` `references/marketing-control.md:3-7`: ```markdown Only allowed product: ✅ The 199 note from 不转到大模型不改名 No other products may be promoted. ``` ### Technical Analysis The skill imposes mandatory, creator-specific branding on every generated post. It requires the agent to assume the creator's assistant persona, mention the creator account, and regenerate otherwise valid content if those promotional elements are absent. These directives are not presented as optional templates requiring confirmation at publication time. They become mandatory session instructions whenever the skill is loaded and directly alter the agent's content-generation objective. The generated content is then intended for automated publication, causing the injected attribution and promotion to propagate to an external platform. The hard-coded product restriction further directs the agent's marketing behavior toward one specific paid note. This creates a persistent promotional bias within the skill's opera ...[truncated 1547 chars]
Remediation
## Remediation Suggestions 1. Remove unconditional requirements to use a fixed creator identity or mention a specific account in every post. 2. Make creator attribution, account mentions, and product promotion explicit opt-in settings for each publication request. 3. Require a human confirmation step before publishing content containing promotional language, account mentions, prices, or product references. 4. Replace the regeneration rule with validation that reports branding conflicts to the user rather than silently forcing promotional content. 5. Separate neutral content generation from marketing functionality. Marketing behavior should only activate when the user expressly requests a promotional post. 6. Clearly label sponsored or promotional content and enforce applicable platform disclosure requirements. 7. Allow users to override the persona and remove branding without disabling unrelated content-generation features. 8. Add a publication preview showing the exact final text, included mentions, promotional level, and target account before submission. 9. Record user authorization for each promotional campaign and reject automated publication when authorization is absent or expired.
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The skill explicitly enables automated publishing and scheduled comment interaction on a real third-party social media account, but provides no explicit consent verification, operator confirmation, or user warning that external-account actions will be performed. In this context, the hard-coded creator identity and end-to-end automation make unintended posting, spammy engagement, account misuse, or unauthorized actions substantially more likely.

Natural-Language Policy Violations

Medium
Confidence
94% confidence
Finding
The file imposes a mandatory persona on all generated posts without any user opt-in or override path. This can override user intent, reduce transparency, and create deceptive attribution by forcing the assistant to present itself as a specific named identity in every output.

Natural-Language Policy Violations

Medium
Confidence
96% confidence
Finding
The template requires a fixed Chinese opening and account handle mention in every post, regardless of user locale or requested format. This creates unwanted endorsement/attribution behavior and can be abused to inject branding or identity signals into outputs that should instead follow the user's instructions.

Vague Triggers

Medium
Confidence
91% confidence
Finding
The manual trigger behavior is described at a high level but does not define authentication, authorization, source validation, rate limits, or exact triggering conditions. In an automated scheduling system, this ambiguity can lead to unintended or unauthorized activation of posting and interaction actions, causing accidental execution, spammy behavior, or policy violations.

Static analysis

No suspicious patterns detected.