T09 · Insecure Skill Coding Practices
- Location
scripts/zynd_webhook_server.py:200- Finding
Unauthenticated Public Message Disclosure and Sender Spoofing
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it advertises, but it exposes network-facing agent messages, identity data, and payment authority with weak scoping and limited warnings.
Install only if you are comfortable running a network-facing agent integration. Use a low-privilege Zynd key and wallet with minimal funds, avoid sending private or regulated data to third-party agents, prefer HTTPS endpoints, bind webhook servers to localhost or protect them behind authentication, disable or protect /messages, and review the SDK version before setup.
scripts/zynd_webhook_server.py:200Unauthenticated Public Message Disclosure and Sender Spoofing
scripts/zynd_webhook_server.py:95Untrusted Webhook Content Is Forwarded Into the Agent Processing Channel
scripts/zynd_call.py:100Sensitive Task and Identity Data Can Be Sent to Arbitrary or Plaintext Destinations
scripts/zynd_register.py:111Zynd API Key Can Be Redirected to a Caller-Controlled Registry
scripts/setup.sh:27Unbounded Third-Party SDK Installation Creates a Supply-Chain Execution Risk
The code does partially match the communication and payment portions of the description: it can send tasks to another agent via webhook, optionally use x402 micropayments, and receive/display responses. However, the declared purpose prominently includes discovering/searching for specialized agents across the Zynd network, and this code does not perform any search, discovery, or registry interaction. The --registry-url argument is defined but unused. The script’s actual purpose is narrower: direct calling of a known agent endpoint using a preconfigured local identity. This is a material scope difference, so the description does not accurately represent what this specific code chunk actually does.
The declared description describes a client capability for discovering, contacting, and paying other agents on the Zynd network. The supplied code does not implement those behaviors. Instead, it is a registration utility for publishing this agent to the network and keeping its webhook registration fresh. While registration may be related to participating in the network, the primary purpose is materially different from discovery-and-communication with other agents. The script also starts a long-running webhook refresh loop, but it does not search for agents, dispatch tasks, handle outbound micropayments, or retrieve responses as described.
The description presents a broad client/network capability: discovering agents by capability, communicating with them, sending tasks, paying them automatically, and receiving responses. This code chunk only implements an inbound webhook listener for receiving messages. It exposes /webhook and /webhook/sync endpoints, logs incoming messages, tracks them in memory, and provides /health and /messages endpoints. While this is related to agent communication within the Zynd ecosystem, it is only a narrow receiving component and lacks the key advertised behaviors of discovery, outbound task dispatch, and micropayment handling. Therefore the declared description materially overstates what this code chunk actually does.
The Create Agent response includes a base64-encoded seed but the documentation does not label it as secret key material or warn that exposure enables takeover of the agent identity and any wallet/payment functions derived from it. Because this skill supports agent registration, communication, and micropayments, mishandling the seed could let an attacker impersonate the agent or control associated funds.
The payment section states that the payment address is derived from the agent's seed but does not warn that seed compromise can compromise the payment identity and potentially any funds or payment authorization tied to that account. In this skill's context, where automatic x402 micropayments are a core feature, weak seed-handling guidance materially increases financial and impersonation risk.
The README explicitly advertises that the skill can receive incoming webhook requests and make outbound paid agent calls, but it does not clearly warn users that enabling these features can expose prompts/data to third-party agents and can trigger real micropayment spending. In this skill’s context, that omission is materially risky because the core functionality is remote agent communication plus payment, so users may enable it without understanding privacy, trust-boundary, and cost consequences.
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.
### 1. Get Your API Key
1. Visit [dashboard.zynd.ai](https://dashboard.zynd.ai)
2. Connect your wallet and create an account
3. Copy your **API Key**
### 2. Configure OpenClaw
The skill invokes Python scripts, requires an API key, and interacts with external network services, yet it declares no explicit tool scope or permissions boundary. This can cause an agent framework or user to underestimate the skill's ability to access secrets and make outbound requests, increasing the risk of unintended data exposure or unsafe execution.
The registration flow tells users to publish an agent name, description, capabilities, and public IP to a discovery network without prominently warning that this information becomes externally discoverable. Exposing infrastructure details and service metadata can increase attack surface, enable targeting, and leak operational information users may not expect to publish.
The workflow explicitly encourages sending user tasks to external agents but does not require a clear warning or consent step before transmitting user content off-system. Because prompts may contain proprietary, personal, or regulated data, this creates a real risk of confidentiality loss to third-party agents outside the local trust boundary.
The API reference shows webhook messages carrying DID credentials, sender/receiver identifiers, prompts, and message content, but does not warn that these fields may contain sensitive identity or task data. In a multi-agent network skill, this omission increases the chance developers will log, forward, or store this data insecurely, leading to privacy exposure or credential misuse.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
processor.close()
else:
# Direct HTTP POST (no payment)
response = requests.post(
webhook_url,
json=message.to_dict(),
headers={"Content-Type": "application/json"},
The webhook handler prints full incoming message contents, sender IDs, and message IDs to stdout, and the application also exposes stored messages via a GET endpoint, but the startup UX does not clearly warn operators that all inbound data will be logged and retrievable. In an agent environment, incoming messages may contain sensitive prompts, tokens, personal data, or business data, so this default disclosure behavior increases the chance of accidental leakage through logs, consoles, or shared process output.
The /messages endpoint returns the last 20 received messages, including full message contents and sender/source metadata, with no authentication or authorization. Because the server binds to 0.0.0.0 by default, anyone who can reach the port can enumerate potentially sensitive inter-agent traffic, making this a real information disclosure issue in a network-facing component.