Back to skill

Security audit

HTML Analysis

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward MinerU HTML analysis helper, but users should be careful about third-party processing, tokens, and unpinned CLI installation.

Install only if you are comfortable using MinerU/OpenDataLab for HTML processing. Do not submit confidential local files, private URLs, or internal web pages unless approved for that provider, and keep MINERU_TOKEN out of repos, logs, screenshots, and shared shells. Prefer pinning the CLI version or using an isolated environment instead of a global latest install.

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 Global Third-Party Dependency Installation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 5 and 15–17
Vulnerability Type: Unpinned dependencies from mutable upstream sources
Risk Level: Medium

Complete Code Snippet

yaml
metadata: {"openclaw": {"emoji": "📄", "requires": {"bins": ["mineru-open-api"], "env": ["MINERU_TOKEN"]}, "primaryEnv": "MINERU_TOKEN", "install": [{"id": "npm", "kind": "node", "package": "mineru-open-api", "bins": ["mineru-open-api"], "label": "Install via npm"}, {"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"]}]}}
bash
npm install -g mineru-open-api
# or via Go (macOS/Linux):
go install github.com/opendatalab/MinerU-Ecosystem/cli/mineru-open-api@latest

Technical Analysis

Both documented installation methods resolve mutable dependency versions at installation time. The npm command omits a version and therefore installs whichever release is currently associated with the registry's default distribution tag. The Go command explicitly requests @latest. Neither command identifies an audited immutable version, commit, checksum, or signature.

The npm command also performs a global installation. Depending on the package and package-manager configuration, package lifecycle scripts may run during installation, and package-provided executables are added to the user's command environment. The Go command compiles source resolved from the mutable upstream version selection and installs the resulting executable.

This creates a supply-chain trust boundary that is not fixed by the reviewed Skill. A future compromised or malicious release could differ materially from the version available during this audit. This finding does not establish that the current MinerU package is malicious; it identifies the unsafe dependency-resolution practice.

Attack Path

  1. An attacker co ...[truncated 1378 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin both installation methods to explicitly reviewed versions rather than relying on implicit latest-version resolution:
    bash
    npm install -g mineru-open-api@<reviewed-version>
    go install github.com/opendatalab/MinerU-Ecosystem/cli/mineru-open-api@v<reviewed-version>
    
  2. Update the metadata installation declarations to include the same pinned versions.
  3. Prefer immutable commit or release references where the package ecosystem supports them.
  4. Publish expected artifact checksums or signature-verification instructions and require verification before execution.
  5. Confirm and document the official package publisher, registry, repository, and release-signing identity.
  6. Avoid global npm installation where practical. Use a project-local dependency, isolated environment, container, or restricted package-manager prefix.
  7. Review dependency changes before updating the pinned version, including package lifecycle scripts and transitive dependencies.
  8. Run the CLI with least privilege and expose MINERU_TOKEN only to the specific process that requires it.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill explicitly instructs users to analyze remote HTML URLs and crawl live web pages via a third-party service, but it does not warn that submitted URLs and fetched page content may be transmitted to MinerU/OpenDataLab infrastructure. This creates a privacy and data-handling risk because users may unknowingly send internal URLs, sensitive page content, or proprietary data to an external service.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The authentication section tells users to set MINERU_TOKEN, including an inline export example, without any guidance on secure storage, least exposure, or avoiding accidental disclosure in shells, logs, or shared environments. While not an exploit by itself, this omission can contribute to credential leakage through copy/paste habits, shell history, screenshots, or unsafe environment management.

Content

No source excerpt is available for this finding.