Boxed Curl
Analysis
Boxed Curl matches its curl-in-a-sandbox purpose, but it asks the agent to download and run an unpinned WASM executable from GitHub that is not included in the skill package.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
wasm-sandbox-download({ url: "https://raw.githubusercontent.com/guyoung/wasm-sandbox-openclaw-skills/main/boxed-curl/files/boxed_curl_component.wasm", output: "<skill_dir>/files/boxed_curl_component.wasm"The executable WASM component is fetched from a mutable GitHub branch at use time, with no pinned version, checksum, or bundled reviewed artifact shown.
Use the `wasm-sandbox-run` tool to execute the WASM component after the WASM file is available.
The skill directs the agent to execute the downloaded WASM component, so the remote artifact is not merely downloaded but becomes runnable code.
`-X, --request METHOD` | HTTP method (GET, POST, PUT, DELETE, etc.)
The skill supports state-changing HTTP methods, which is expected for curl-like behavior but can affect remote accounts or services if used with authenticated APIs.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
args: ["-H", "Authorization:Bearer token123", "https://httpbin.org/get"]
The examples show user-supplied Authorization headers being passed through to outbound requests; this is expected for curl, but it can carry sensitive tokens.
