ClawHub
Back to skill

Security audit

Webhook Receiver

Security checks for vulnerabilities and agentic risk

Overview

The skill does what it claims, but its examples encourage unsafe full webhook logging and direct remote script execution.

Install with pip or uv from a trusted package source instead of running the remote shell commands. Use this skill only for controlled webhook testing unless you add verification, authentication, redaction, and log retention limits. Do not log full headers or bodies for OAuth, payment, production, or personal-data webhooks.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (5)

Missing User Warnings

Medium
Confidence
94% confidence
Finding
This is a real issue: the skill exposes a public internet-facing webhook endpoint and explicitly recommends logging full request headers and bodies. Webhook payloads commonly contain secrets, bearer tokens, signatures, PII, API keys, or business data, so verbose logging can create secondary sensitive-data exposure in terminal history, log files, or agent outputs.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The skill instructs users to execute remote installer scripts directly via shell and PowerShell pipes without any integrity verification, pinning, or warning. If the remote server, transport, DNS, or hosting chain is compromised, arbitrary code will run immediately on the user's machine or agent environment.

Ssd 3

Medium
Confidence
95% confidence
Finding
This is a true positive because the example handler prints all incoming headers and request bodies from arbitrary external senders. In webhook contexts, those values often include authentication material, signed payload metadata, personal data, and event contents that should not be broadly exposed or retained.

Ssd 3

Medium
Confidence
95% confidence
Finding
The note explicitly advises logging full request headers and body for debugging, which is unsafe for a publicly exposed webhook receiver. This increases the chance of accidental disclosure of secrets or regulated data to logs, consoles, observability systems, or downstream AI tooling.

External Script Fetching

High
Category
Supply Chain
Content
## CLI Reference

The `aitun` command (installed via `pip install aitun`, or alternatively `curl -fsSL https://aitun.cc/install.sh | bash` / `irm https://aitun.cc/install.ps1 | iex` on Windows) accepts these flags:

| Flag | Description |
|---|---|
Confidence
98% confidence
Finding
The CLI reference normalizes direct execution of a remotely fetched script via `curl ... | bash` and `irm ... | iex`, which is a well-known arbitrary code execution risk. Including it in reference material makes the unsafe practice easier to copy-paste and more dangerous in an agent skill context where users may execute commands verbatim.

Static analysis

No suspicious patterns detected.