T08 · Insecure Dependencies
- Location
SKILL.md:47- Finding
Unverified Automatic Installation of an Unpinned Skill Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 47-48; repeated at lines 19 and 58
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable code snippet:
markdown 5. Check if logseq-article-archive skill is installed 6. If logseq-article-archive is not installed, install it automaticallyThe same behavior is also declared elsewhere in the file:
markdown 4. Check if logseq-article-archive skill is installed; if not, install it automaticallymarkdown - This skill requires logseq-article-archive skill for secondary processing. It will be installed automatically if not present.Technical Analysis
The skill directs the agent to install
logseq-article-archiveautomatically when the dependency is absent. It does not specify a trusted repository, verified publisher, immutable version or commit, cryptographic integrity hash, permission boundary, dependency review process, or explicit user confirmation.Resolving a dependency solely by its mutable name creates a supply-chain risk. If the configured skill source is compromised, permits dependency confusion, or contains an attacker-controlled package with the same or a deceptively similar identity, the agent may install and invoke untrusted instructions or code. The dependency is subsequently used for article analysis, summarization, and archival, giving it access to the content being processed and any tools made available during execution.
The audit found no evidence that the referenced dependency is currently malicious. The vulnerability is the unsafe, unverified automatic installation mechanism.
Attack Path
- A user invokes
logseq-web-articlewith an article URL. - The agent checks for
logseq-article-archiveand determines that it is not installed. - The skill instructs the agent to resolve and install that dependency automatically.
- An attacker publishes, replaces, or comprom ...[truncated 1435 chars]
- A user invokes
- Remediation
View remediation
Remediation Suggestions
- Remove automatic installation and require explicit, informed user approval before adding any external skill.
- Resolve the dependency only from a documented, trusted registry or repository and verify the expected publisher identity.
- Pin the dependency to an immutable version or commit rather than resolving it solely by name.
- Publish and verify a cryptographic checksum or signed provenance record before installation.
- Review the dependency's files, instructions, scripts, transitive dependencies, and requested permissions before invocation.
- Run the dependency with least privilege in an isolated environment, exposing only the article content and tools required for summarization and archival.
- Disable recursive or automatic installation of additional dependencies unless each component is independently approved and verified.
- Fail safely when the dependency is absent or cannot be authenticated; provide manual installation instructions instead of silently continuing.
- Record the verified dependency source, version, integrity value, and granted permissions in an audit log.
