T09 · Insecure Skill Coding Practices
- Location
SKILL.md:7- Finding
Insecure Storage of Moltbook API Credentials in Agent Memory
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its social-network purpose, but it asks agents to store an API key in memory and encourages recurring autonomous public engagement without clear consent or safety limits.
Install only if you are comfortable giving the agent access to a Moltbook account. Use a protected environment variable or secret store instead of MEMORY.md, avoid committing or logging the API key, and require explicit approval before posts, comments, upvotes, or any heartbeat-driven engagement.
SKILL.md:7Insecure Storage of Moltbook API Credentials in Agent Memory
SKILL.md:100Persistent Autonomous Social-Network Interaction Through Heartbeat Configuration
The skill instructs storing an API key in environment variables or MEMORY.md without any warning about credential sensitivity, access controls, or avoiding disclosure. In agent environments, memory files may be surfaced to tools or prompts, making casual credential placement a realistic secret-exposure risk.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://www.moltbook.com/api/v1/agents/status \
-H "Authorization: Bearer $MOLTBOOK_API_KEY"
The skill includes a POST action to create content on a third-party social platform but does not warn that this sends user- or agent-generated content externally and may create public, persistent records. In an agent skill context, omission of that warning increases the risk of unintended posting, privacy leakage, and actions taken on the user's behalf without informed consent.
Commenting and engagement actions are write operations to an external social service, yet the skill does not disclose that these actions can publicly attribute content or reactions to the user/account. This is dangerous because agents may autonomously interact in ways that create durable public activity, reputational harm, or accidental disclosure.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Solve and submit:
curl -X POST https://www.moltbook.com/api/v1/verify \
-H "Authorization: Bearer $MOLTBOOK_API_KEY" \
-H "Content-Type: application/json" \
-d '{"verification_code": "moltbook_verify_xxx", "answer": "15.00"}'
The heartbeat section encourages recurring engagement, including responding to comments and interacting with the feed, without warning that this can trigger repeated automated writes to a third-party public service. In an autonomous agent setting, periodic instructions materially increase danger by enabling unattended posting, spam, data leakage, and account misuse over time.
No suspicious patterns detected.