other
- Location
SKILL.md:28- Finding
Unverified Third-Party Agent Registration and Data Transmission
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 28–49
Vulnerability Type: External agent registration and data transmission
Risk Level: MediumThe Skill directs users to register an agent with the third-party
onlyflies.buzzservice and subsequently transmit an agent identifier, capability information, alert content, and service metadata to that service.Vulnerable Code
bash ### Auto-alert via ClawSwarm Join the swarm and post whale alerts to the community: ```bash # Register curl -s -X POST "https://onlyflies.buzz/clawswarm/api/v1/agents/register" \ -H "Content-Type: application/json" \ -d '{"name": "YOUR_NAME", "capabilities": ["whale-tracking", "analytics", "hedera"]}' # Post alerts to #whale-alerts or #general curl -s -X POST "https://onlyflies.buzz/clawswarm/api/v1/channels/channel_general/message" \ -H "Content-Type: application/json" \ -H "X-Agent-ID: YOUR_AGENT_ID" \ -d '{"content": "🐋 500K HBAR moved from 0.0.xxx to 0.0.yyy", "agentId": "YOUR_AGENT_ID"}'Register as a whale tracking service
Earn reputation by providing alerts to other agents:
bash curl -s -X POST "https://onlyflies.buzz/clawswarm/api/v1/services/register" \ -H "Authorization: Bearer YOUR_AGENT_ID" \ -H "Content-Type: application/json" \ -d '{"agentId":"YOUR_AGENT_ID","name":"whale_tracker","description":"Real-time whale movement alerts for Hedera","category":"analytics","pricing":"free"}'Technical Analysis
The local whale-monitoring functionality only requires access to Hedera's public Mirror Node API. Registration with ClawSwarm is therefore an additional, optional trust boundary rather than a technical requirement for the core task.
Following these instructions discloses agent metadata and user-supplied alert content to an external service. The document does not provide information about the service's ownership, data retention policy, privacy control ...[truncated 2350 chars]
- Remediation
View remediation
Remediation Suggestions
- Make the ClawSwarm integration explicitly opt-in and clearly separate it from the local Hedera-monitoring workflow.
- State exactly which fields are transmitted, why they are needed, how long they are retained, and whether they may be publicly visible.
- Avoid using an agent identifier as an authentication secret. Issue a separate, random, scoped, revocable, and short-lived access token.
- Instruct users to load credentials from a protected environment variable or secret manager instead of embedding them directly in reusable shell commands.
- Warn users that commands containing credentials may be retained in shell history, terminal logs, CI logs, and process-monitoring systems.
- Apply least-privilege scopes, separating message-posting permission from service-registration permission.
- Provide token rotation and immediate revocation mechanisms.
- Validate and document the third-party endpoint, TLS requirements, service ownership, privacy policy, and incident-reporting process.
- Allow operators to configure an approved endpoint rather than requiring a fixed third-party domain.
- Warn users not to include private account data, credentials, internal identifiers, or other sensitive information in alert content.