Back to skill

Security audit

Word To Markdown

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Office-document-to-Markdown helper, but users should understand it installs an external CLI and uploads documents to MinerU for processing.

Install only if you trust the MinerU CLI distribution path you choose, and use it only with documents you are comfortable sending to MinerU's cloud API. For sensitive business, legal, or personal files, prefer an isolated environment or a locally processed alternative.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:5
Finding

Unpinned Third-Party CLI Dependencies

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 5
Vulnerability Type: Unpinned third-party dependencies
Risk Level: Medium

Vulnerable Code

yaml
metadata: {"openclaw":{"emoji":"📑","requires":{"bins":["mineru-open-api"]},"install":[{"id":"npm","kind":"node","package":"mineru-open-api","bins":["mineru-open-api"],"label":"Install via npm"},{"id":"uv","kind":"uv","package":"mineru-open-api","bins":["mineru-open-api"],"label":"Install via uv"},{"id":"go","kind":"go","package":"github.com/opendatalab/MinerU-Ecosystem/cli/mineru-open-api","bins":["mineru-open-api"],"label":"Install via go install","os":["darwin","linux"]}]}}

Technical Analysis

The skill offers three installation methods for mineru-open-api, but none identifies an immutable, reviewed release. The npm and Python package references omit version constraints, while the Go module reference omits a version or commit. Consequently, installation can resolve to whatever release the upstream registry or repository serves at that time.

This creates a supply-chain risk because the installed code may differ from the code originally evaluated with the skill. A compromised maintainer account, malicious package release, repository compromise, or unexpected upstream change could introduce executable behavior without any modification to this project.

The finding does not establish that the current upstream package is malicious. It identifies the absence of controls that would prevent a future altered release from being installed automatically.

Attack Path

  1. An attacker compromises an upstream package publisher, registry account, source repository, or release process.
  2. The attacker publishes a malicious version under the existing mineru-open-api package or module name.
  3. A user or agent installs the dependency through one of the unpinned installation entries in SKILL.md.
  4. The package manager resolves and installs the attacker-contr ...[truncated 913 chars]
Remediation
View remediation

Remediation Suggestions

  • Pin npm and Python installations to specific, reviewed versions rather than resolving the latest available release.
  • Pin the Go installation to a reviewed semantic version or immutable commit identifier.
  • Use lockfiles and integrity hashes where the package ecosystem supports them.
  • Verify package provenance, publisher identity, release signatures, and checksums before installation.
  • Perform dependency and malware scanning on each approved release before updating the pinned version.
  • Execute the converter with least privilege in an isolated environment that has access only to the document being processed and its designated output directory.
  • Require explicit user consent before uploading sensitive documents to the external MinerU service.
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Static analysis

No suspicious patterns detected.