Security audit

Mobile Appium Test

Security checks for vulnerabilities and agentic risk

Overview

The skill is for legitimate Android Appium testing, but it presents broad Appium relaxed-security mode as a normal setup step without enough warning or scoping.

Install only if you are comfortable with Appium/ADB controlling a USB-authorized Android device. Prefer starting Appium on 127.0.0.1 without `--relaxed-security`, enable only specific insecure features if truly required, avoid exposing port 4723, stop the server after testing, and avoid running the global npm install with administrator privileges.

A.I.G

Vulnerability Patterns

Insecure DependenciesIntroduces malicious components through unsafe dependency sources
Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
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

Findings (2)

T09 · Insecure Skill Coding Practices

Error

Location: SKILL.md:43
Finding: Appium Server Runs with Broad Relaxed-Security Features Enabled
Content: View full analysis
Remediation: View remediation

T08 · Insecure Dependencies

Note

Location: SKILL.md:20
Finding: Unpinned Global npm Package Installation
Content: View full analysis
Remediation: View remediation
``` - Prefer a project-local development dependency governed by a committed lockfile instead of a global installation. - Install packages from the expected npm registry and verify package provenance and integrity before use. - Review the pinned package's lifecycle scripts and dependency tree. - Avoid running npm with administrator or root privileges. - Periodically update the pinned version through a controlled review and testing process rather than resolving the latest release automatically. ]]>

SkillSpector

Vulnerability Patterns

Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
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)

Tool Parameter Abuse

High

Category: Tool Misuse
Confidence: 80% confidence
Finding: Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
Content: Scanner excerpt · SKILL.md (reported line 58)May include surrounding context.
md
| Send keys | `POST /session/{id}/element/{id}/value` | | Take screenshot | `GET /session/{id}/screenshot` | | Get page source | `GET /session/{id}/source` | | Quit session | `DELETE /session/{id}` | ## Typical Workflow

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The skill explicitly recommends starting Appium with --relaxed-security, which weakens Appium's security controls and can enable access to insecure or sensitive features if the server is reachable by other local users or the network. In a testing skill this may be operationally convenient, but presenting it as a standard step without any warning, scope limitation, or safer default increases the chance of unsafe deployment.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.