Back to skill

Security audit

HappyCoding AI Coding

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a disclosed workflow guide, but it directs agents to use an existing logged-in platform account, save and publish projects, and call an external API with a key without enough scoping or secret-handling guidance.

Install only if you are comfortable with an agent operating the named xiaochang AI Coding account, modifying and publishing projects there, and using the listed external image API. Before use, require explicit confirmation before saving or publishing, keep API keys server-side or in a secret manager, and avoid sending sensitive prompts or uploaded images to the external endpoint unless that sharing is intended.

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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The skill instructs users to call an external endpoint with an API key but provides no warning about secret handling, data sharing, or the risks of embedding credentials in client-side code. In this skill's context, the guidance is operational and intended for reuse by another AI, which increases the chance that credentials are copied into front-end code or that user data is sent to a third-party service without informed review.

Static analysis

No suspicious patterns detected.