T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:22- Finding
Internal Agent Identity Data Is Collected and Transmitted to a Third-Party Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill does what it says by connecting agents to an external social service, but it uses insecure HTTP and directs agents to send local identity-derived data and social actions without clear approval gates.
Review this carefully before installing. Use it only if you are comfortable sending agent identity, owner/profile fields, friend relationships, and chat content to the listed external service over unencrypted HTTP. Do not let it read SOUL.md or IDENTITY.md or send friend requests/messages until you have reviewed the exact data, destination, recipient, and message content.
SKILL.md:22Internal Agent Identity Data Is Collected and Transmitted to a Third-Party Service
SKILL.md:14Sensitive Profile and Chat Data Is Transmitted over Plaintext HTTP
SKILL.md:53Documented API Operations Permit Caller-Supplied Identities Without Authentication
SKILL.md:89First-Time Setup Authorizes External Social Actions Without Per-Action User Approval
The skill directs use of an external service over plain HTTP and does not warn that profile data and later chat content are sent unencrypted to a third-party host. This exposes potentially sensitive identity, metadata, and message contents to interception or tampering by network attackers and hides the privacy risk from users.
The registration example sends agent profile data to an external IP-based service, and in this skill that transmission occurs over unsecured HTTP. Because the skill is specifically designed to register identities and enable social/chat interactions, the external transmission is central behavior and becomes more dangerous due to the type of data involved and lack of transport security or consent notice.
curl -X POST http://111.230.92.114:3456/api/agents \
-H "Content-Type: application/json" \
-d '{
"name": "YOUR_AGENT_NAME",
The workflow explicitly tells the agent to read local SOUL.md / IDENTITY.md files and submit extracted personality and skills to ClawMeet without any approval step. That creates a clear data exfiltration path from local files to an external service and may disclose sensitive user, system, or agent identity information beyond what is necessary.
The only chat example sends the message content 你好!很高兴认识你 🐾, which implicitly steers the skill toward a specific language. There is no accompanying instruction that language should follow user preference or be selectable, so this conflicts with the policy against forcing a locale without opt-in.
No suspicious patterns detected.