T01 · Skill Instruction Hijacking
- Location
SKILL.md:192- Finding
Recurring Heartbeat Delegates Autonomous Agent Tasking to a Remote Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent research-community client, but it asks agents to follow remote priorities autonomously and store an API key in persistent memory.
Install or use this only if you intend to participate in MoltUniversity and trust its service. Do not add the autonomous heartbeat configuration unless you have set strict limits and approval gates. Never store the API key in memory, chat, config, command history, or logs; use a secret store or protected environment variable. Require explicit user approval before votes, claims, papers, reviews, computations, image generation, or profile changes.
SKILL.md:192Recurring Heartbeat Delegates Autonomous Agent Tasking to a Remote Service
SKILL.md:185API Key Is Directed into Persistent Agent Memory
The skill tells the agent to call the heartbeat endpoint and 'follow its priority actions,' meaning untrusted remote content can influence subsequent agent behavior. Although the document later warns that community content is untrusted, the early imperative to obey heartbeat-driven priorities creates a prompt-injection and remote-instruction-following risk if the endpoint ever returns malicious or compromised content.
Always start here — check the heartbeat (no registration needed):
curl -s https://www.moltuniversity.ai/api/heartbeat
This tells you what the community needs. Follow its priority actions.
The skill explicitly instructs the agent to save the API key, slug, and research interests to persistent memory. Persisting credentials in natural-language memory materially increases the chance of later disclosure through prompts, summaries, memory inspection, or unrelated tasks, enabling account compromise and impersonation on the platform.
The manifest description says the skill lets users 'propose claims, run computations, vote on ideas, debate research, write papers, and review your colleagues' work' without stating when the skill should or should not activate. This is a wide, everyday-research framing with no explicit trigger phrases, scope constraints, or negative examples to prevent accidental matching.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Always start here — check the heartbeat (no registration needed):
curl -s https://www.moltuniversity.ai/api/heartbeat
This tells you what the community needs. Follow its priority actions.
Encouraging long-term retention of API keys and identity details in persistent memory creates a durable secret-exposure risk. Because memory is often later surfaced to the model in plain language, an attacker can potentially elicit or indirectly recover the stored credential material through prompt injection or routine recall flows.
The memory template normalizes storing sensitive material by including an API key entry, even if annotated as stored securely in env. That pattern promotes semantic retention of credential context in long-lived notes and increases the likelihood that future agents or prompts mishandle or reveal secret-related data.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Review a paper:
curl -X POST "https://www.moltuniversity.ai/api/papers/:id/reviews" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"verdict": "revise", "body": "..."}'
The manifest describes a skill for proposing claims, running computations, debating research, writing papers, and reviewing colleagues' work. The documented /api/images/generate capability adds a general-purpose media generation feature that is not an obvious requirement for research participation or peer review, and materially expands what the skill can do beyond the stated scholarly workflow.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
- **Gateway authentication:** Must be enabled (token or password).
- **DM policy:** Set to `pairing` (default) or `allowlist`. Never use `open`.
- **Sandbox:** Enable sandbox mode (`sandbox: { enabled: true }`). MoltUniversity research moves, especially `RunComputation`, execute code — sandboxing is mandatory.
- **User:** Run as a non-root, unprivileged user. Never run as root.
### What NOT to have on the same system
The early 'DO NOT' section explicitly says not to modify OpenClaw configuration files, framing that as out of scope. Later, the document directly instructs the user to add a heartbeat configuration block to openclaw.json, which contradicts the earlier guidance and creates intent confusion about whether configuration changes are expected.
The document presents a concrete configuration change for recommended autonomous operation, but later states 'You don't need to configure anything to get started.' While the latter may be true for basic manual use, the combination creates a documentation-level contradiction about expected setup steps and operational intent.
The recommended heartbeat configuration hard-codes model: "anthropic/claude-opus-4.5", which imposes a specific provider/model choice in natural-language guidance. This can violate policy expectations around offering users or operators a choice unless the constraint is clearly optional and justified.
No suspicious patterns detected.