T08 · Insecure Dependencies
- Location
SKILL.md:20- Finding
Unpinned Third-Party Skill Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 20–22
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
yaml external_skills: - name: financial-report-fetcher slug: "@tuobadaidai/financial-report-fetcher" install: "openclaw skills install @tuobadaidai/financial-report-fetcher"The same unpinned installation instruction is repeated at lines 137–139 and line 540:
bash openclaw skills install @tuobadaidai/financial-report-fetcherTechnical Analysis
The Skill instructs users or agents to install
@tuobadaidai/financial-report-fetcherwithout specifying an immutable version, commit, checksum, or cryptographic signature. Consequently, the installed implementation may differ from the dependency that was originally reviewed or intended.The dependency is expected to retrieve and process external financial reports. Its implementation is not included in this project, so its integrity and runtime behavior could not be verified during this audit. If the package owner, distribution account, registry, or a future mutable release is compromised, malicious behavior could be introduced through the dependency supply chain.
This finding does not establish that the named dependency is currently malicious. The risk arises from trusting and installing mutable, unaudited third-party code.
Attack Path
- An attacker compromises the dependency publisher, package account, or relevant distribution channel.
- The attacker publishes a modified release under the existing dependency identifier.
- A user invokes the documented industry-research workflow while the dependency is unavailable locally.
- The documentation prompts installation using:
openclaw skills install @tuobadaidai/financial-report-fetcher. - Because no version or digest is pinned, the package manager resolves the attacker-controlled release.
- The dependency executes within the permissions available to the host age ...[truncated 837 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a reviewed, immutable version rather than resolving the latest mutable release.
- Prefer an immutable content digest or audited commit identifier where the Skill ecosystem supports it.
- Verify package signatures or checksums before installation and fail closed on verification errors.
- Document the authoritative registry and publisher identity to reduce dependency-confusion and impersonation risks.
- Require explicit user approval before installing or updating any third-party Skill.
- Audit the dependency and its transitive dependencies before deployment.
- Run the dependency with least privilege, restricting filesystem access, credentials, outbound networking, and available tools to those needed for report retrieval.
- Maintain a trusted-version allowlist and prevent automatic upgrades until new releases have been reviewed.
- Vendor the audited dependency into a controlled repository when licensing and maintenance constraints permit.
