Back to skill

Security audit

Claw Keyboard

Security checks for vulnerabilities and agentic risk

Overview

This keyboard-control skill matches its stated purpose, but it needs Review because it installs mutable native binaries without pinned verification and suggests a broad persistent Linux device permission rule.

Install only if you trust the publisher and the GitHub release channel for the native binary. Prefer a version-pinned release with a digest enforced by the installer, and do not add the Linux udev rule as written without narrowing it to the specific keyboard/interface or using a dedicated group or active-session access mechanism.

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (2)

T03 · Remote Payload Retrieval and Execution

Error
Location
SKILL.md:20
Finding

Mutable Unverified Native Executables Are Retrieved from Remote Releases

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 20-51
Vulnerability Type: Remote payload retrieval and execution
Risk Level: High

Vulnerable Code

yaml
install:
  - id: darwin-arm64
    kind: download
    url: https://github.com/clawdevice/claw-keyboard/releases/latest/download/claw-keyboard-darwin-arm64
    bins: [claw-keyboard]
    label: macOS Apple Silicon
    os: [darwin]
  - id: darwin-amd64
    kind: download
    url: https://github.com/clawdevice/claw-keyboard/releases/latest/download/claw-keyboard-darwin-amd64
    bins: [claw-keyboard]
    label: macOS Intel
    os: [darwin]
  - id: linux-amd64
    kind: download
    url: https://github.com/clawdevice/claw-keyboard/releases/latest/download/claw-keyboard-linux-amd64
    bins: [claw-keyboard]
    label: Linux x86_64
    os: [linux]
  - id: linux-arm64
    kind: download
    url: https://github.com/clawdevice/claw-keyboard/releases/latest/download/claw-keyboard-linux-arm64
    bins: [claw-keyboard]
    label: Linux ARM64
    os: [linux]
  - id: windows-amd64
    kind: download
    url: https://github.com/clawdevice/claw-keyboard/releases/latest/download/claw-keyboard-windows-amd64.exe
    bins: [claw-keyboard]
    label: Windows x86_64
    os: [win32]
  - id: windows-arm64
    kind: download
    url: https://github.com/clawdevice/claw-keyboard/releases/latest/download/claw-keyboard-windows-arm64.exe
    bins: [claw-keyboard]
    label: Windows ARM64
    os: [win32]

Technical Analysis

The Skill retrieves precompiled native executables through GitHub's mutable releases/latest path. The effective executable can therefore change after the Skill itself has been reviewed, without any modification to SKILL.md.

No immutable release version or expected platform-specific digest is included in the installation metadata. Although line 134 states that checksums are available on the Re ...[truncated 2190 chars]

Remediation
View remediation

Remediation Suggestions

  1. Replace every releases/latest URL with an immutable, explicitly versioned release URL.
  2. Add a platform-specific SHA-256 digest to the installation metadata and require the installer to reject any artifact that does not match it.
  3. Do not rely solely on a checksum fetched from the same mutable release. Pin the expected digest in the reviewed Skill package or verify a signed release using a public key distributed through an independent trusted channel.
  4. Publish provenance attestations and use a hardened CI release workflow with protected environments and short-lived publishing credentials.
  5. Prefer reproducible builds and publish the corresponding source revision and build instructions so release artifacts can be independently verified.
  6. Update dependencies through a review process that changes both the pinned version and digest, making payload changes visible in the Skill diff.

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:133
Finding

Recommended udev Rule Grants World-Writable Access to Broad HID Device Scope

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 133
Vulnerability Type: Excessive local device permissions
Risk Level: Medium

Vulnerable Code

text
On Linux, you may need udev rules to access USB HID devices without root. Create `/etc/udev/rules.d/99-claw-keyboard.rules` with `SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1a86", MODE="0666"` and run `sudo udevadm control --reload-rules`.

Technical Analysis

The recommended udev rule sets matching hidraw device nodes to mode 0666, granting read and write access to every local user. It matches only vendor ID 1a86; it does not constrain access to a particular product, interface, serial number, or the documented vendor HID usage page and usage.

As a result, the rule can expose all matching HID interfaces from that vendor, including devices or interfaces unrelated to the keyboard-management task. World-writable access is broader than necessary because the Skill only needs access for the interactive user or service account running claw-keyboard.

Installing the rule requires an explicit sudo operation and is presented as optional guidance, so the Skill does not silently elevate privileges. Once installed, however, the rule establishes an unnecessarily permissive system-wide access-control policy that persists across sessions and device reconnections.

Attack Path

  1. An administrator or authorized user follows the Skill documentation and creates the proposed udev rule using sudo.
  2. The udev configuration is reloaded, and a device with vendor ID 1a86 is connected or re-enumerated.
  3. Its matching hidraw nodes receive mode 0666.
  4. Any unprivileged local account or process opens those nodes without belonging to a trusted device-access group.
  5. The process reads HID traffic or writes crafted reports to the keyboard or another matching device.
  6. Depending on the exposed device protocol, the process can inspect device responses or ...[truncated 740 chars]
Remediation
View remediation

Remediation Suggestions

  1. Replace MODE="0666" with MODE="0660" and assign access to a dedicated group containing only authorized users, for example through GROUP="claw-keyboard".
  2. Where supported by the target desktop environment, use TAG+="uaccess" to grant access only to the active local session instead of every local account.
  3. Narrow the rule with verified product, interface, or other stable device attributes in addition to the vendor ID.
  4. Provide commands for inspecting udev attributes so users can create a rule specific to their compatible keyboard.
  5. Document that the rule is optional, requires administrator review, persists after installation, and should be removed when the Skill is no longer used.
  6. Continue to run the utility as an unprivileged user; do not recommend running the entire Agent or executable as root as an alternative.
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)

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

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

md
- The tool auto-discovers keyboards by scanning for HID interfaces with UsagePage `0xFF60` and Usage `0x61`, then verifying via a challenge-response handshake.
- Not all keyboards expose the vendor HID interface. If `discover` finds nothing, the keyboard may not support this protocol.
- On macOS, you may need to grant HID access permission to the terminal application in System Settings > Privacy & Security > Input Monitoring.
- On Linux, you may need udev rules to access USB HID devices without root. Create `/etc/udev/rules.d/99-claw-keyboard.rules` with `SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1a86", MODE="0666"` and run `sudo udevadm control --reload-rules`.
- SHA256 checksums for all binaries are available in the `SHA256SUMS` file on the GitHub Releases page. Verify after downloading: `shasum -a 256 -c SHA256SUMS`.
- Use `--json` flag for machine-readable output.