Back to skill

Security audit

hermes-desktop-customization

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed guide for locally customizing and rebuilding Hermes Desktop source, with one documentation inconsistency about update handling that users should verify before following.

Before installing or using this skill, treat it as guidance for modifying a local Hermes Desktop source checkout. Follow its approval-first workflow, verify the current git branch and clean working tree yourself, and be cautious with the update section because the documented update paths conflict.

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
  • 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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Intent-Code Divergence

Medium
Confidence
96% confidence
Finding
The 'Verification' section states that plain `hermes update` would switch away from a non-main branch and that `hermes update --branch desktop-custom` fails for a local-only branch, recommending `update_in_place` instead. Later, the 'Update Survival' section says `hermes update` auto-stashes and restores uncommitted edits and recommends `hermes update --branch desktop-custom`, which directly conflicts with the earlier documented behavior and could mislead a user into performing the wrong update procedure.

Static analysis

No suspicious patterns detected.