ClawHub
Back to skill

Security audit

open-connect-control

Security checks for vulnerabilities and agentic risk

Overview

ClawScan rates this skill benign with high confidence: the completed scans found no AIG issues, and the one credential-related alert appears in setup guidance that says not to embed access tokens.

If you install it, follow the setup guidance: use your host's supported OAuth connection and do not put access tokens in skill or plugin files. The scan covered the single Markdown component completely; executable-code analyzers were not applicable, so this result is not a guarantee of zero risk.

A.I.G

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

SkillSpector

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

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
## Client setup

The remote MCP endpoint is `https://open-connect.site/mcp`. Use the host's supported HTTP MCP connector and complete its OAuth flow. Keep the existing App identity and account; do not embed access tokens into plugin files. ChatGPT, Codex, Hermes and other clients have different connection and skill-loading mechanisms. Verify each host's current support rather than claiming that installing in one installs in all.

On phones, prefer the hosted HTTP connection and provider OAuth in the same browser profile. A local CLI, stdio server or desktop executor needs its own supported runtime. Desktop setup does not prove Android or iOS execution. If a host has a stale tool schema, refresh the existing connection through supported host settings and rediscover tools; do not create duplicates to bypass a missing refresh control.