Back to skill

Security audit

Wanx

Security checks for vulnerabilities and agentic risk

Overview

The skill is coherent for controlling Wanx through OOMOL, but its fallback setup tells an agent to install a CLI by piping a remote script directly into a shell.

Review this skill before installing if the oo CLI is not already present. Prefer installing the oo CLI manually from official documentation with version and integrity checks instead of allowing an agent to run the remote install one-liners. Once the CLI is installed and connected, the Wanx action workflow itself appears purpose-aligned, with write actions requiring confirmation.

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

External Script Fetching

High
Category
Supply Chain
Confidence
95% confidence
Finding

The skill instructs users/agents to install software by piping a remotely fetched script directly into a shell (curl ... | bash). This creates a supply-chain and remote-code-execution risk: if the remote host, TLS trust chain, distribution pipeline, or script content is compromised, arbitrary code will run immediately with the user's privileges. In the context of an agent skill, this is more dangerous because the skill normalizes executing the command as a fallback step during operation rather than requiring a separately verified installation process.

Content

Scanner excerpt · SKILL.md (reported line 57)May include surrounding context.

Static analysis

No suspicious patterns detected.