T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Global Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:4,SKILL.md:14-16
Vulnerability Type: Supply-chain risk from mutable, unpinned dependencies
Risk Level: MediumThe skill metadata declares
mineru-open-apiwithout a fixed version: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"]}]}}The documented installation commands also select mutable upstream releases:
bash npm install -g mineru-open-api # or via Go (macOS/Linux): go install github.com/opendatalab/MinerU-Ecosystem/cli/mineru-open-api@latestTechnical Analysis
Neither installation method identifies a reviewed, immutable dependency version. The npm command resolves the registry's current package release and installs it globally. The Go command explicitly uses
@latest, causing its resolved source to change as new upstream versions are published.Consequently, the effective executable installed by users may differ from the dependency reviewed when this skill was published. If the package registry, upstream repository, release process, or maintainer credentials are compromised, an attacker could distribute altered code under the expected package name. npm installation scripts may execute during installation, while malicious code in either distribution can execute when the installed
mineru-open-apibinary is invoked.No evidence shows that the current upstream dependency is malicious. The finding concerns the absence of version and integrity controls, which leaves a viable supply-chain exploitation path.
Attack Path
...[truncated 1722 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin both installation methods to exact, reviewed releases:
- Replace the unversioned npm package with an exact version such as
mineru-open-api@X.Y.Z. - Replace the Go
@latestselector with a reviewed semantic version or immutable commit identifier.
- Replace the unversioned npm package with an exact version such as
- Verify dependency authenticity and integrity:
- Record and validate npm integrity metadata or trusted artifact checksums.
- Verify Go module checksums and ensure the expected module repository and release tag are used.
- Document the expected package publisher and upstream repository.
- Avoid global npm installation where practical. Prefer a project-local dependency, isolated package environment, container, or dedicated low-privilege account.
- Review the pinned dependency and its transitive dependencies before updating. Use an explicit update process rather than automatically accepting the newest release.
- Avoid installing packages with administrator or root privileges. If elevated installation cannot be avoided, separate installation from execution and verify the artifact beforehand.
- Restrict the OCR process to only the files, environment variables, and network destinations it requires. Provide the MinerU token only for the duration of the operation.
- Document how authentication tokens and uploaded documents are transmitted, stored, and retained by the external OCR service so users can make informed decisions about sensitive data.
- Pin both installation methods to exact, reviewed releases:
