T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned Third-Party Dependency Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:4andSKILL.md:14
Vulnerability Type: Unpinned executable dependency
Risk Level: MediumVulnerable Code
yaml metadata: {"openclaw":{"emoji":"🔍","requires":{"bins":["bbot","nmap"]},"install":[{"id":"bbot","kind":"pipx","packages":["bbot"],"label":"Install bbot via pipx"}]}}bash pipx install bbotTechnical Analysis
The Skill installs
bbotfrom the configured Python package index without specifying a reviewed version or validating package integrity. Consequently, the exact code installed can change after the Skill has been audited.Although no evidence indicates that the current
bbotpackage is malicious, relying on an unpinned executable dependency exposes users to compromised upstream releases, unexpected breaking changes, and package-index or account compromise. The installed package is subsequently invoked byscripts/recon.py, causing its code to execute with the privileges of the user running the Skill.Attack Path
- An attacker compromises the upstream package publisher, release process, or configured package index.
- The attacker publishes a malicious or backdoored version under the expected
bbotpackage name. - A user installs the Skill dependency using
pipx install bbot. - Because no version or integrity constraint is present, the malicious release is selected.
- The payload executes during package use when the reconnaissance script invokes the installed
bbotexecutable.
Impact Assessment
A compromised dependency could execute arbitrary code with the privileges of the user running the Skill. This could permit access to user-readable files, modification of user-writable files, credential theft from the user's environment, unauthorized network activity, or falsification of reconnaissance results.
The dependency does not inherently provide administrative privileges, so the immediate scope is g ...[truncated 189 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
bbotto a specifically reviewed version in both the Skill metadata and installation documentation. - Use an internally approved package index or trusted mirror where possible.
- Verify package hashes or signatures when supported by the installation mechanism.
- Establish a controlled dependency-update process that includes source review, vulnerability scanning, and functional testing.
- Document the exact supported package version so the metadata and manual installation instructions remain consistent.
- Run reconnaissance tools in a restricted environment with only the filesystem and network permissions required for the scan.
- Pin
