ClawHub
Back to skill

Security audit

wpf-desktop

Security checks for vulnerabilities and agentic risk

Overview

This Windows app development guide needs review because it recommends stopping the desktop manager without explaining the wider impact or requiring user confirmation.

Review the desktop-recovery instructions before use. Prefer recovery limited to the affected application, and require explicit confirmation with a display-impact warning before stopping dwm.exe. Test overlays and input hooks in an isolated Windows session. The concern is unsafe troubleshooting guidance, with no evidence of malicious intent.

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
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • 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 (1)

Recommends terminating the desktop window manager without warning about desktop-session disruption.

Medium
Category
Output Handling
Confidence
90% confidence
Finding

The document repeatedly presents terminating dwm.exe as the only recovery method without warning that this forcibly interrupts desktop composition and can disrupt the interactive session or remote access. Although the surrounding WPF troubleshooting and preventive guidance are legitimate, an agent following this advice could turn an application hang into broader desktop disruption; this is unsafe operational guidance rather than evidence of malicious intent.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.