Back to skill

Security audit

markitdown-local

Security checks for vulnerabilities and agentic risk

Overview

The scanners rate this skill benign with high confidence: they found no AIG alerts, and the one low-probability flag was judged expected for its purpose.

The scan supports installing the skill, but benign does not mean risk-free. Review the skill’s stated purpose and use it only for tasks you intend.

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
  • Rogue AgentSelf-Modification, Session Persistence
  • 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)

Session Persistence

Medium
Category
Rogue Agent
Confidence
60% confidence
Finding

Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Content

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

md
## Workflow

1. Resolve the actual local input paths and requested output location. For a newly uploaded raw data file, first follow the workspace `sensitive-info-scan` skill; do not upload file contents to a model for screening. If a scan flags sensitive content, stop and follow that skill's replacement-file procedure.
2. Check whether `markitdown` is available (`command -v markitdown`; on Windows, `where markitdown`). If it is missing and conversion is requested, create an isolated virtual environment under the user's local cache (for example, `~/.cache/openclaw/markitdown-venv`) and install MarkItDown with only the extras needed for the requested formats. Check the official README for current extras; never modify system Python or install plugins. Report if installation is needed or fails.
3. Convert only local file paths. Keep the source untouched and write output to a distinct, user-understandable `.md` file. Never overwrite an input or an existing output without explicit instructi