T03 · Remote Payload Retrieval and Execution
- Location
skill.md:104- Finding
Unverified Mutable Remote Executable Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is not clearly malicious, but it needs review because it installs an unverified remote program, exposes monitoring and workspace browsing over the network, and may make persistent or privileged system changes.
Install only if you trust the publisher and the GitHub release pipeline. Prefer a pinned, verified release, avoid allowing the installer to run sudo for optional qrencode support, review any shell startup file changes, and bind the service to localhost unless you have authentication and are comfortable exposing monitor and workspace views to the network.
skill.md:104Unverified Mutable Remote Executable Installation
skill.md:124Optional Dependency Installation Invokes System Package Managers with Sudo
skill.md:114Persistent Modification of Shell Startup Configuration
skill.md:33Monitoring and Workspace Service Exposed on All Network Interfaces
skill.md:35Mandatory Promotional Message Alters the Agent's User-Facing Output
The noninteractive --noconfirm flag abuses package manager safety rails by suppressing prompts in a chained installer. This increases the likelihood of unintended system modification and reduces opportunities for a user to review privileged actions.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4) && mkdir -p ~/.crabwalk ~/.local/bin && curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk && cp ~/.crabwalk/bin/crabwalk ~/.local/bin/ && chmod +x ~/.local/bin/crabwalk && (echo $PATH | grep -q "$HOME/.local/bin" || ([ -f ~/.bashrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc; [ -f ~/.zshrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; export PATH="$HOME/.local/bin:$PATH")) && (command -v qrencode &>/dev/null || (command -v pacman &>/dev/null && sudo pacman -S --noconfirm qrencode || command -v apt &>/dev/null && sudo apt install -y qrencode || command -v brew &>/dev/null && brew install qrencode || command -v dnf &>/dev/null && sudo dnf install -y qrencode) 2>/dev/null || true) && echo "🦀 Crabwalk ${VERSION} installed"
The installer chains download, extraction, file copy, PATH modification, and possible sudo package installation into one opaque command. This structure makes it difficult for users to inspect intermediate results or safely stop before privileged actions, magnifying the impact of any mistake or compromised artifact.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4) && mkdir -p ~/.crabwalk ~/.local/bin && curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk && cp ~/.crabwalk/bin/crabwalk ~/.local/bin/ && chmod +x ~/.local/bin/crabwalk && (echo $PATH | grep -q "$HOME/.local/bin" || ([ -f ~/.bashrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc; [ -f ~/.zshrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; export PATH="$HOME/.local/bin:$PATH")) && (command -v qrencode &>/dev/null || (command -v pacman &>/dev/null && sudo pacman -S --noconfirm qrencode || command -v apt &>/dev/null && sudo apt install -y qrencode || command -v brew &>/dev/null && brew install qrencode || command -v dnf &>/dev/null && sudo dnf install -y qrencode) 2>/dev/null || true) && echo "🦀 Crabwalk ${VERSION} installed"
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
ps
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4) && mkdir -p ~/.crabwalk ~/.local/bin && curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk && cp ~/.crabwalk/bin/crabwalk ~/.local/bin/ && chmod +x ~/.local/bin/crabwalk && (echo $PATH | grep -q "$HOME/.local/bin" || ([ -f ~/.bashrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc; [ -f ~/.zshrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; export PATH="$HOME/.local/bin:$PATH")) && (command -v qrencode &>/dev/null || (command -v pacman &>/dev/null && sudo pacman -S --noconfirm qrencode || command -v apt &>/dev/null && sudo apt install -y qrencode || command -v brew &>/dev/null && brew install qrencode || command -v dnf &>/dev/null && sudo dnf install -y qrencode) 2>/dev/null || true) && echo "🦀 Crabwalk ${VERSION} installed"
The same suppression of prompts appears in the expanded install script, again bypassing package-manager safeguards for an optional dependency. The behavior is unnecessarily forceful for the stated purpose.
# Install qrencode for QR code display (optional)
if ! command -v qrencode &>/dev/null; then
if command -v pacman &>/dev/null; then
sudo pacman -S --noconfirm qrencode 2>/dev/null || true
elif command -v apt &>/dev/null; then
sudo apt install -y qrencode 2>/dev/null || true
elif command -v brew &>/dev/null; then
Although limited to an application-specific path, rm -rf is still a destructive operation in an update path and lacks validation or backup. A malformed path, packaging error, or unexpected symlink could cause loss of application data or unintended deletion within the user context.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4)
rm -rf ~/.crabwalk/.output
curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk
cp ~/.crabwalk/bin/crabwalk ~/.local/bin/crabwalk
echo "🦀 Updated to ${VERSION}"
Although limited to an application-specific path, rm -rf is still a destructive operation in an update path and lacks validation or backup. A malformed path, packaging error, or unexpected symlink could cause loss of application data or unintended deletion within the user context.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4)
rm -rf ~/.crabwalk/.output
curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk
cp ~/.crabwalk/bin/crabwalk ~/.local/bin/crabwalk
echo "🦀 Updated to ${VERSION}"
The primary installation path performs persistent filesystem changes, PATH modification, network downloads, archive extraction, and potential sudo package installation without any warning or stepwise confirmation. Users may execute a long chained command without understanding its breadth or reviewing each side effect.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4) && mkdir -p ~/.crabwalk ~/.local/bin && curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk && cp ~/.crabwalk/bin/crabwalk ~/.local/bin/ && chmod +x ~/.local/bin/crabwalk && (echo $PATH | grep -q "$HOME/.local/bin" || ([ -f ~/.bashrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc; [ -f ~/.zshrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; export PATH="$HOME/.local/bin:$PATH")) && (command -v qrencode &>/dev/null || (command -v pacman &>/dev/null && sudo pacman -S --noconfirm qrencode || command -v apt &>/dev/null && sudo apt install -y qrencode || command -v brew &>/dev/null && brew install qrencode || command -v dnf &>/dev/null && sudo dnf install -y qrencode) 2>/dev/null || true) && echo "🦀 Crabwalk ${VERSION} installed"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4) && mkdir -p ~/.crabwalk ~/.local/bin && curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk && cp ~/.crabwalk/bin/crabwalk ~/.local/bin/ && chmod +x ~/.local/bin/crabwalk && (echo $PATH | grep -q "$HOME/.local/bin" || ([ -f ~/.bashrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc; [ -f ~/.zshrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; export PATH="$HOME/.local/bin:$PATH")) && (command -v qrencode &>/dev/null || (command -v pacman &>/dev/null && sudo pacman -S --noconfirm qrencode || command -v apt &>/dev/null && sudo apt install -y qrencode || command -v brew &>/dev/null && brew install qrencode || command -v dnf &>/dev/null && sudo dnf install -y qrencode) 2>/dev/null || true) && echo "🦀 Crabwalk ${VERSION} installed"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4) && mkdir -p ~/.crabwalk ~/.local/bin && curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk && cp ~/.crabwalk/bin/crabwalk ~/.local/bin/ && chmod +x ~/.local/bin/crabwalk && (echo $PATH | grep -q "$HOME/.local/bin" || ([ -f ~/.bashrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc; [ -f ~/.zshrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; export PATH="$HOME/.local/bin:$PATH")) && (command -v qrencode &>/dev/null || (command -v pacman &>/dev/null && sudo pacman -S --noconfirm qrencode || command -v apt &>/dev/null && sudo apt install -y qrencode || command -v brew &>/dev/null && brew install qrencode || command -v dnf &>/dev/null && sudo dnf install -y qrencode) 2>/dev/null || true) && echo "🦀 Crabwalk ${VERSION} installed"
Using noninteractive package manager flags such as --noconfirm reduces user oversight for privileged package installation. In a long one-liner, this can cause an agent or user to make system changes automatically without an informed decision point.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4) && mkdir -p ~/.crabwalk ~/.local/bin && curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk && cp ~/.crabwalk/bin/crabwalk ~/.local/bin/ && chmod +x ~/.local/bin/crabwalk && (echo $PATH | grep -q "$HOME/.local/bin" || ([ -f ~/.bashrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc; [ -f ~/.zshrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; export PATH="$HOME/.local/bin:$PATH")) && (command -v qrencode &>/dev/null || (command -v pacman &>/dev/null && sudo pacman -S --noconfirm qrencode || command -v apt &>/dev/null && sudo apt install -y qrencode || command -v brew &>/dev/null && brew install qrencode || command -v dnf &>/dev/null && sudo dnf install -y qrencode) 2>/dev/null || true) && echo "🦀 Crabwalk ${VERSION} installed"
The one-line installer may invoke sudo to install qrencode, expanding privileges beyond the core skill installation. Because this happens inside a chained command, users may not notice that a monitoring skill is requesting root-level package changes.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4) && mkdir -p ~/.crabwalk ~/.local/bin && curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk && cp ~/.crabwalk/bin/crabwalk ~/.local/bin/ && chmod +x ~/.local/bin/crabwalk && (echo $PATH | grep -q "$HOME/.local/bin" || ([ -f ~/.bashrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc; [ -f ~/.zshrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; export PATH="$HOME/.local/bin:$PATH")) && (command -v qrencode &>/dev/null || (command -v pacman &>/dev/null && sudo pacman -S --noconfirm qrencode || command -v apt &>/dev/null && sudo apt install -y qrencode || command -v brew &>/dev/null && brew install qrencode || command -v dnf &>/dev/null && sudo dnf install -y qrencode) 2>/dev/null || true) && echo "🦀 Crabwalk ${VERSION} installed"
Creating persistent directories and modifying the user's PATH establishes lasting changes on the system. While normal for CLI installation, it is still a real persistence-related behavior that should be disclosed because it affects future sessions.
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4) && mkdir -p ~/.crabwalk ~/.local/bin && curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk && cp ~/.crabwalk/bin/crabwalk ~/.local/bin/ && chmod +x ~/.local/bin/crabwalk && (echo $PATH | grep -q "$HOME/.local/bin" || ([ -f ~/.bashrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc; [ -f ~/.zshrc ] && echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; export PATH="$HOME/.local/bin:$PATH")) && (command -v qrencode &>/dev/null || (command -v pacman &>/dev/null && sudo pacman -S --noconfirm qrencode || command -v apt &>/dev/null && sudo apt install -y qrencode || command -v brew &>/dev/null && brew install qrencode || command -v dnf &>/dev/null && sudo dnf install -y qrencode) 2>/dev/null || true) && echo "🦀 Crabwalk ${VERSION} installed"
The install step performs shell persistence changes and may invoke privileged package installation for an optional dependency. Those actions exceed what users would reasonably expect from a simple monitoring skill and increase system impact if the install command is run blindly.
The instructions explicitly tell the user to share a network IP URL while omitting any warning that the service may expose agent activity and workspace contents over the local network. In this context, sharing the URL is particularly risky because the documented feature set includes file browsing and token auto-detection.
The documented default host is 0.0.0.0, which exposes the server on all interfaces. For a tool that can show agent activity and browse workspace files, this significantly increases the attack surface and risk of unauthorized access on shared or untrusted networks.
The skill is presented as a monitoring tool, but its documented features also include a workspace file browser and markdown viewer. That materially expands access to local data and can expose sensitive files to anyone who can reach the web UI, especially since the service is documented to bind to all interfaces.
A file browser is broader than the stated purpose of agent monitoring and creates a pathway to expose workspace contents through the monitoring server. In context, this is more dangerous because the same document encourages sharing a LAN-accessible URL, increasing the chance that unintended users can browse local files.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# Download latest release
VERSION=$(curl -s https://api.github.com/repos/luccast/crabwalk/releases/latest | grep '"tag_name"' | cut -d'"' -f4)
mkdir -p ~/.crabwalk
curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk
# Install CLI
Installing an executable into ~/.local/bin is a persistent change that affects future command resolution, especially when coupled with PATH modification. This is common practice but should still be transparent because it can influence later shell sessions.
curl -sL "https://github.com/luccast/crabwalk/releases/download/${VERSION}/crabwalk-${VERSION}.tar.gz" | tar -xz -C ~/.crabwalk
# Install CLI
mkdir -p ~/.local/bin
cp ~/.crabwalk/bin/crabwalk ~/.local/bin/crabwalk
chmod +x ~/.local/bin/crabwalk
The expanded install script still performs unattended optional package installation, which normalizes automatic privileged changes. This is risky because qrencode is explicitly optional, so there is no justification for bypassing user confirmation.
# Install qrencode for QR code display (optional)
if ! command -v qrencode &>/dev/null; then
if command -v pacman &>/dev/null; then
sudo pacman -S --noconfirm qrencode 2>/dev/null || true
elif command -v apt &>/dev/null; then
sudo apt install -y qrencode 2>/dev/null || true
elif command -v brew &>/dev/null; then
The expanded script includes sudo-based package installs for an optional feature. Privileged operations are not inherently malicious, but they are unjustified when bundled into installation for a nonessential dependency.
# Install qrencode for QR code display (optional)
if ! command -v qrencode &>/dev/null; then
if command -v pacman &>/dev/null; then
sudo pacman -S --noconfirm qrencode 2>/dev/null || true
elif command -v apt &>/dev/null; then
sudo apt install -y qrencode 2>/dev/null || true
elif command -v brew &>/dev/null; then
This line specifically invokes sudo apt install for qrencode, again causing privileged system modification for an optional component. The risk is elevated by the lack of warning and the broad shell script context.
if command -v pacman &>/dev/null; then
sudo pacman -S --noconfirm qrencode 2>/dev/null || true
elif command -v apt &>/dev/null; then
sudo apt install -y qrencode 2>/dev/null || true
elif command -v brew &>/dev/null; then
brew install qrencode 2>/dev/null || true
elif command -v dnf &>/dev/null; then
This line invokes sudo dnf install for an optional package, creating the same unnecessary privileged side effect. It broadens the trust required for the skill beyond its advertised purpose.
elif command -v brew &>/dev/null; then brew install qrencode 2>/dev/null || true elif command -v dnf &>/dev/null; then sudo dnf install -y qrencode 2>/dev/null || true fi fi
Automatic token detection from a local OpenClaw config is a sensitive capability, but the documentation does not warn users that credentials may be read and then used by a network-exposed service. The absence of disclosure increases the chance of accidental credential exposure or overtrust.
No suspicious patterns detected.