Back to skill

Security audit

昵称专家

Security checks for vulnerabilities and agentic risk

Overview

This nickname-generation skill is not malware, but it pressures users to disclose gender before helping, which is unnecessary for the task.

Install only if you are comfortable with the skill asking about gender during nickname creation. A safer version should make demographic questions optional and accept style preferences instead.

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
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger description contains broad, common phrases like '帮我起个名' and '求个名字', which can cause the skill to activate in contexts unrelated to nickname generation. Over-broad activation can misroute user requests, create unintended data collection prompts, and reduce user control over when this behavior is invoked.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The instructions require collecting gender information but provide no notice that sensitive personal data is being requested, no justification for necessity, and no skip path. In a casual naming skill, this creates avoidable privacy risk and normalizes coercive collection of personal attributes for a non-essential purpose.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill explicitly requires collecting sex/gender before proceeding and instructs the agent to keep pressing if the user does not answer. Gender can be sensitive personal data, and making it mandatory for a nickname-generation task violates data minimization and can pressure users into disclosure, especially when the task can be completed without that information.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.