Back to skill

Security audit

agent-desktop-linux

Security checks for vulnerabilities and agentic risk

Overview

ClawScan marks this Linux desktop reference skill suspicious because scanners report guidance to disable Electron sandbox protections and an action that closes GNOME Calculator, which was not declared in its stated purpose.

Review the reported sandbox-disabling advice and the undeclared application-closing action before installing. The scanners did not report malicious intent, but the verdict is suspicious and Skillspector's analysis was partial because three local references could not be resolved.

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
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The supplied shell command changes desktop application state by closing GNOME Calculator. Although the description mentions lifecycle documentation, it does not declare performing application lifecycle actions. The code therefore has a materially different purpose from the advertised reference guide.

Content

No source excerpt is available for this finding.

Recommends launching Electron apps with --no-sandbox without warning that this disables Chromium's sandbox protections.

Medium
Category
Output Handling
Confidence
98% confidence
Finding

The guide recommends --no-sandbox as a routine Electron compatibility workaround without explaining that it disables Chromium sandbox protections. If the application processes attacker-controlled content, a renderer compromise could consequently gain access to the desktop user's files and session resources without the normal sandbox barrier.

Content

No source excerpt is available for this finding.

Unsafe Defaults

Medium
Category
Tool Misuse
Confidence
70% confidence
Finding

Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.

Content

Scanner excerpt · references/capture-and-clipboard.md (reported line 104)May include surrounding context.

md
- The helper must sit beside the `agent-desktop` binary and be a regular
  executable file, not a symlink, owned by the user or root. Neither it nor its
  directory may be group-writable, even when the group appears private; the file
  must not be world-writable. Remove group-write permission from both the helper
  and its directory before using a build made with a group-writable umask. A
  world-writable directory is accepted only with the sticky bit and without
  group-write permission. A 777 copy is refused with `PLATFORM_NOT_SUPPORTED`, "writable by

Unsafe Defaults

Medium
Category
Tool Misuse
Confidence
70% confidence
Finding

Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.

Content

Scanner excerpt · references/capture-and-clipboard.md (reported line 106)May include surrounding context.

md
directory may be group-writable, even when the group appears private; the file
  must not be world-writable. Remove group-write permission from both the helper
  and its directory before using a build made with a group-writable umask. A
  world-writable directory is accepted only with the sticky bit and without
  group-write permission. A 777 copy is refused with `PLATFORM_NOT_SUPPORTED`, "writable by
  others". npm installs and release archives ship it in place. A binary copied
  alone cannot set the clipboard: `PLATFORM_NOT_SUPPORTED` names the missing

Recommends launching Electron with sandboxing disabled without warning about the security impact.

Medium
Category
Output Handling
Confidence
98% confidence
Finding

The troubleshooting table presents --no-sandbox as the solution when Electron's chrome-sandbox helper is not setuid, without disclosing the security tradeoff or offering safer alternatives. Following this guidance removes Chromium sandbox protections, potentially allowing exploitation of untrusted application content to compromise the user's desktop session.

Content

No source excerpt is available for this finding.