Back to skill

Security audit

Jike

Security checks for vulnerabilities and agentic risk

Overview

This is a placeholder music-integration skill with no executable code, persistence, credential handling, or hidden behavior.

This skill appears safe to install as a placeholder, but it is not functionally complete. Before relying on a future version, review the updated artifact for concrete trigger conditions, what music/account data it can access, and whether any automation actions require explicit user approval.

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
  • 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)

Natural-Language Policy Violations

Low
Confidence
72% confidence
Finding
The skill description and headings are primarily written in Chinese, with no indication that the user can choose another language or locale. If organizational policy requires avoiding language constraints without user opt-in, this presents a natural-language policy concern.

Vague Triggers

Low
Confidence
84% confidence
Finding
The phrase '适用于需要音乐娱乐自动化和智能化的场景' describes the skill as applicable to a very broad class of situations, but does not define specific invocation phrases, scope limits, or exclusion conditions. In a markdown skill description, this can create ambiguity about when the skill should activate versus when it should not.

Static analysis

No suspicious patterns detected.