T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:86- Finding
Unpinned Remote Dependency Is Downloaded and Executed with Wallet Access
- Content
View full analysis
/dev/null cp -r /tmp/bankr-skills-temp/bankr ~/.clawdbot/skills/bankr rm -rf /tmp/bankr-skills-temp BANKR_SCRIPT="$HOME/.clawdbot/skills/bankr/scripts/bankr.sh" chmod +x "$BANKR_SCRIPT" fi ``` ### Technical Analysis The setup procedure clones the current default branch of an external GitHub repository, copies its contents into the local skills directory, and marks its Bankr script as executable. The dependency is not pinned to a reviewed commit or release, and no checksum, signature, or integrity verification is performed. This is a remote payload retrieval risk because the effective code installed by the skill can change after this project has been reviewed. The downloaded Bankr script is subsequently invoked with instructions to approve token spending and submit blockchain transactions. Consequently, malicious upstream code would execute in a security-sensitive wallet workflow. The procedure also suppresses Git error output and does not verify that the checkout came from the expected commit before copying it. ### Attack Path 1. An attacker compromises the upstream repository, maintainer account, release process, or default branch. 2. The attacker modifies the `bankr` directory or `scripts/bankr.sh`. 3. A user runs the documented pre-flight procedure while Bankr is not already installed. 4. The setup clones the attacker-controlled default branch without pinning or integrity verification. 5. The malicious files are copied into `~/.clawdbot/skills/bankr`, and `bankr.sh` is made executable. 6. Later setup or heartbeat opera ...[truncated 949 chars]- Remediation
View remediation
