Back to skill

Security audit

Clawvisual

Security checks for vulnerabilities and agentic risk

Overview

The skill is coherent for carousel generation, but it needs Review because it can store and transmit API keys and user content, auto-start a detached local service, and invoke broad MCP tools without enough safeguards.

Install only if you are comfortable with a global npm CLI that can start a local web/MCP service and store API keys on disk. Keep `CLAWVISUAL_MCP_URL` on localhost or HTTPS, avoid submitting sensitive or proprietary content unless the configured LLM/MCP service is approved, secure or remove `~/.clawvisual/config.json`, and treat the raw MCP call command as developer-level access.

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 (3)

T09 · Insecure Skill Coding Practices

Error
Location
scripts/clawvisual-mcp-client.mjs:248
Finding

Sensitive RPC Data Can Be Transmitted over Cleartext HTTP

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/clawvisual-mcp-client.mjs:41
Finding

API Keys Are Stored in Plaintext without Enforced Restrictive Permissions

Content
View full analysis
"); } const config = readLocalConfig(); config[key] = value; writeLocalConfig(config); print({ ok: true, action: "set", key, value: maskConfigValue(key, value), config_file: CONFIG_FILE }); } ``` ### Technical Analysis The `set` command stores `CLAWVISUAL_LLM_API_KEY` and `CLAWVISUAL_API_KEY` as plaintext values in `~/.clawvisual/config.json`. Although command output masks designated secrets, the underlying file remains unencrypted. More importantly, neither `mkdirSync` nor `writeFileSync` specifies restrictive permission modes. Newly created permissions therefore depend on the process umask. If the file already exists with permissive permissions, rewriting it does not repair those permissions. This can expose credentials to other local users or processes on systems with permissive umasks, shared home directories, weak container boundaries, or previously misconfigured files. ### Attack Path 1. A user runs `clawvisual set CLAWVISUAL_LLM_API_KEY
Remediation
View remediation

T08 · Insecure Dependencies

Warning
Location
SKILL.md:14
Finding

Installation Instructions Use an Unpinned Global npm Package

Content
View full analysis
Remediation
View remediation
`. 2. Record and verify package integrity metadata where the installation system supports it. 3. Publish checksums or signed provenance for reviewed releases. 4. Use a lockfile for repository-local installations and review dependency changes before updates. 5. Avoid elevated global installation where possible; prefer a project-local installation or an isolated execution environment. 6. Disable npm lifecycle scripts with `--ignore-scripts` when they are not required, or explicitly document and audit every required lifecycle script. 7. Link the package to a verifiable source repository and document the expected publisher identity. ]]>
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Behavioral ASTexec() Call, eval() Call, Dynamic Import
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Findings (9)

MCP Config Access

High
Category
Agent Snooping
Confidence
80% confidence
Finding

Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.

Content

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

md
- `clawvisual initialize`: probe/start local service and print Web URL.
- `clawvisual status`: check service identity (must be `clawvisual-mcp`).
- `clawvisual tools`: list MCP tools.
- `clawvisual convert --input <text_or_url> [--slides auto|1-8] [--ratio 4:5|1:1|9:16|16:9] [--lang <code>]`
- `clawvisual status --job <job_id>`: query job state and result.
- `clawvisual revise --job <job_id> --instruction <text> [--intent rewrite_copy_style|regenerate_cover|regenerate_slides]`

Context-Inappropriate Capability

High
Category
Not specified by scanner
Confidence
95% confidence
Finding

The client can automatically spawn and detach a local Next.js development server when the MCP endpoint is unavailable. Even though it restricts auto-start to localhost and probes service identity, launching a background subprocess is a materially broader capability than a simple carousel-generation client and can surprise users, create persistence-like behavior during a session, and increase attack surface by exposing a local web service.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
90% confidence
Finding

The skill declares no explicit tool scope or permission boundaries despite requiring environment-variable access and network-capable behavior. In an agent setting, this weakens least-privilege controls and can allow the skill to access secrets or make outbound requests without clear user-visible constraints.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The documentation instructs users to submit URLs or long-form text to an LLM-backed local service but does not warn that this content may be transmitted to an external model provider via configured API URL/key settings. Users may unknowingly send proprietary, personal, or sensitive data to third-party services, creating confidentiality and compliance risks.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

The client persists configuration, including API secrets, into a predictable file under the user's home directory (~/.clawvisual/config.json). While this appears intended for convenience rather than abuse, storing secrets locally expands the skill’s effective capability beyond the stated MCP client role and increases credential exposure risk if file permissions are weak, backups are shared, or the host is multi-user.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The code writes configuration directly to ~/.clawvisual/config.json and supports storing API keys there, but does not warn users at the point of storage that credentials will persist on disk. This is dangerous because users may assume ephemeral use, then unintentionally leave reusable secrets in plaintext or broadly readable local files.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The convert command forces output_language to en-US whenever the user does not explicitly provide --lang. This imposes a specific locale by default rather than offering a neutral choice or explicit opt-in, which can violate language/locale policy requirements.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The generic call command allows invoking arbitrary MCP tool names with arbitrary JSON arguments, bypassing the narrower command surface otherwise exposed by the CLI. In this skill context, that broadens the reachable functionality to whatever the backend MCP server offers, which may include sensitive or unsafe operations not reflected in the manifest or expected by users.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

The code spawns a detached Next.js dev server automatically when initialize/tools/other commands detect the service is unavailable. Although the usage text mentions auto-start for initialize, the subprocess execution affecting the local system is not consistently disclosed at the execution point for other commands that also call ensureServerReady().

Content

No source excerpt is available for this finding.