Back to skill

Security audit

obsidian-toolkit-pro

Security checks for vulnerabilities and agentic risk

Overview

This Obsidian toolkit needs review because its Git workflow can upload private notes and plugin settings without adequate checks.

Before using Git synchronization, confirm the repository and who can access it, preserve existing exclusions, exclude private notes and sensitive plugin settings, and review the staged contents before pushing. Back up the vault and preview bulk changes. The scanner's missing-reference gaps were resolved from the inline instructions; actual repository contents, permissions, and runtime behavior remain unverified.

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
  • 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)

The Git workflow publishes staged vault contents to a remote server without warning about disclosure of private notes.

Medium
Category
Output Handling
Confidence
97% confidence
Finding

The workflow uses git add ., commits, and pushes the vault without reviewing staged files or confirming the remote's access controls. Its minimal ignore list leaves private notes and potentially sensitive plugin configuration eligible for publication, including persistence in Git history. Git synchronization is a legitimate feature and the remote is a user-configured placeholder, so this is an unsafe disclosure default rather than evidence of deliberate exfiltration.

Content

No source excerpt is available for this finding.