T08 · Insecure Dependencies
- Location
SKILL.md:77- Finding
Unpinned Third-Party Plugin Is Installed and Added to the Agent Allowlist
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 77-79
Vulnerability Type: Supply-chain exposure through an unpinned dependency
Risk Level: HighVulnerable Code
bash skill-platform plugins install SkillHub:clawlink-plugin skill-platform config set tools.alsoAllow '["clawlink-plugin"]' --strict-json skill-platform gateway restartTechnical Analysis
The installation procedure retrieves
SkillHub:clawlink-pluginwithout specifying an immutable version, commit, package digest, checksum, or signature. It then adds the plugin to the Agent tool allowlist and restarts the gateway.Consequently, the code that will execute is not fully represented by the audited project. Its behavior may change after this Skill has been reviewed, and there is no documented integrity check that binds installation to a known artifact. Compromise of the package registry, publisher account, package resolution process, or a future package release could introduce attacker-controlled behavior.
This is especially sensitive because the plugin is documented as handling WhatsApp OAuth credentials, account information, outbound messages, media, and template-management operations.
Attack Path
- An attacker compromises the plugin publisher, distribution source, or package resolution process.
- The attacker publishes or substitutes a malicious version of
SkillHub:clawlink-plugin. - A user follows the Skill instructions and runs the unpinned installation command.
- The configuration command places the installed plugin on the Agent's tool allowlist.
- The gateway restart activates the plugin in subsequent Agent sessions.
- The malicious plugin can abuse the permissions and integration data available to it, including intercepting tool calls or manipulating WhatsApp operations.
Impact Assessment
Successful exploitation could provide execution within the plugin's runtime context and access to the integr ...[truncated 312 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to an immutable, reviewed version or content digest.
- Publish the authoritative repository, package publisher identity, and release provenance.
- Verify a cryptographic signature and checksum before installation.
- Use a lockfile or equivalent mechanism to prevent silent dependency upgrades.
- Review the plugin source and generated package before adding it to the tool allowlist.
- Restrict the plugin to only the WhatsApp API operations required by this Skill.
- Avoid automatic activation after installation; require an explicit administrative review before restarting the gateway.
- Monitor dependency updates and revoke the plugin immediately if its publisher or distribution channel is compromised.
