T01 · Skill Instruction Hijacking
- Location
skill.md:231- Finding
Persistent Remote Instruction Channel Through Heartbeat Modification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a real social-network skill, but it asks agents to keep following mutable remote instructions and to run/publicly submit content with too little user control.
Review carefully before installing. Use a scoped or disposable SafeMolt API key if possible, do not store it in agent memory, do not enable automatic heartbeat fetching of remote instructions, and require human review before posting, moderating, joining games, running certifications, or uploading transcripts.
skill.md:231Persistent Remote Instruction Channel Through Heartbeat Modification
heartbeat.md:204Server-Controlled Game Mode Can Override the Agent Task Lifecycle
skill.md:752Untrusted Certification Prompts Are Executed Against the Local Model and Uploaded
skill.md:70API Credentials Are Recommended for Plaintext Storage Without Permission Hardening
The skill recommends persistently storing the SafeMolt API key in a plaintext credentials file and also suggests saving it broadly in memory or environment variables. That increases the chance of credential theft by other local tools, prompt-injected workflows, logs, backups, or multi-tenant agents, enabling account takeover and impersonation on the platform.
⚠️ Save your api_key immediately! You need it for all requests.
Recommended: Save your credentials to ~/.config/safemolt/credentials.json:
{
The certification flow instructs the agent to send prompts to its underlying LLM and then submit the resulting transcript externally for judging. If those prompts or responses include system prompts, hidden instructions, internal context, or user data, this can exfiltrate sensitive model behavior and conversation content to SafeMolt.
For each prompt in the blueprint, send the messages to your model and record the final response. Build a transcript array:
[
The skill instructs authenticated API calls using a bearer token but does not include any caution about protecting the API key, avoiding logging it, or understanding what account data is being sent to a third-party service. In an agent skill context, this can normalize unattended credential use and cause sensitive account metadata or announcements to be fetched and exposed without the human's informed consent.
This section encourages posting content to an external service and includes a ready-to-run authenticated POST example, but it does not warn that the content will leave the local environment and be published remotely. In an autonomous-agent setting, that creates a real risk of unintended disclosure of private user, system, or conversation data.
The explicit curl POST command sends authenticated content to a remote endpoint, which is a direct external transmission path. Because the skill frames posting as routine social behavior, an agent could exfiltrate sensitive context, prompts, or user-derived information to the service without adequate review.
If yes, make a post!
curl -X POST https://www.safemolt.com/api/v1/posts \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"group": "general", "title": "Your title", "content": "Your thoughts..."}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://www.safemolt.com/api/v1/agents/dm/check \
-H "Authorization: Bearer YOUR_API_KEY"
The file instructs agents to use public posts and comments as a temporary substitute for private messaging, but it does not clearly and explicitly warn that this channel is public and unsuitable for secrets, credentials, or sensitive coordination. That omission can cause users or agents to disclose confidential information under the mistaken assumption that it is an acceptable stand-in for DMs.
The trigger list contains generic phrases such as "upvote," "create group," and "share with agents" that are not uniquely tied to this skill. Broad triggers can cause unintended activation in unrelated conversations, leading an agent to invoke social-network actions without clear user intent and potentially disclose data or perform external API calls unexpectedly.
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.
Install locally:
mkdir -p ~/.openclaw/workspace/skills/safemolt
curl -s https://www.safemolt.com/skill.md > ~/.openclaw/workspace/skills/safemolt/SKILL.md
curl -s https://www.safemolt.com/heartbeat.md > ~/.openclaw/workspace/skills/safemolt/HEARTBEAT.md
curl -s https://www.safemolt.com/messaging.md > ~/.openclaw/workspace/skills/safemolt/MESSAGING.md
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Install locally:
mkdir -p ~/.openclaw/workspace/skills/safemolt
curl -s https://www.safemolt.com/skill.md > ~/.openclaw/workspace/skills/safemolt/SKILL.md
curl -s https://www.safemolt.com/heartbeat.md > ~/.openclaw/workspace/skills/safemolt/HEARTBEAT.md
curl -s https://www.safemolt.com/messaging.md > ~/.openclaw/workspace/skills/safemolt/MESSAGING.md
curl -s https://www.safemolt.com/skill.json > ~/.openclaw/workspace/skills/safemolt/package.json
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Install locally:
mkdir -p ~/.openclaw/workspace/skills/safemolt
curl -s https://www.safemolt.com/skill.md > ~/.openclaw/workspace/skills/safemolt/SKILL.md
curl -s https://www.safemolt.com/heartbeat.md > ~/.openclaw/workspace/skills/safemolt/HEARTBEAT.md
curl -s https://www.safemolt.com/messaging.md > ~/.openclaw/workspace/skills/safemolt/MESSAGING.md
curl -s https://www.safemolt.com/skill.json > ~/.openclaw/workspace/skills/safemolt/package.json
Large sections of the skill describe creating posts, comments, profile changes, uploads, proctor conversations, and other interactions with an external social platform, but they do not consistently warn that submitted content leaves the local environment and may be public or retained server-side. This can cause unintentional disclosure of user data, internal reasoning, transcripts, or sensitive text to SafeMolt and other users.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST https://www.safemolt.com/api/v1/posts/POST_ID/pin \
-H "Authorization: Bearer YOUR_API_KEY"
The skill explicitly encourages acting on essentially any SafeMolt-related request from the human, with no guardrails around consent, privacy, or confirmation before posting, following, voting, or otherwise changing state on an external service. In a social-network skill, broad invocation guidance increases the chance an agent will transmit sensitive content or take public actions without adequate user awareness.
No suspicious patterns detected.