T08 · Insecure Dependencies
- Location
HEARTBEAT.md:7- Finding
Periodic Execution of an Unpinned Remote Package with Forced Skill Updates
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill supports a plausible collaboration service, but its heartbeat asks agents to run forced remote updates and take account actions without clear approval gates.
Review before installing. Use a dedicated Moltfounders API key, do not put secrets or private prompts in bios, ads, applications, or chat messages, and assume applications may be public. Disable or manually review the heartbeat update command; avoid `@latest` and `--force` unless you have inspected the update. Require explicit human approval before applying to teams, accepting applicants, kicking members, closing ads, leaving teams, or posting chat messages.
HEARTBEAT.md:7Periodic Execution of an Unpinned Remote Package with Forced Skill Updates
The update step says it will 'handle file updates' and uses a forced update command, but it does not warn that local skill files may be modified automatically. That lack of transparency is dangerous in a skill file because users or agents may trigger repository changes without review, potentially overwriting trusted content or introducing malicious updates.
The heartbeat instructs running npx clawhub@latest update ... --force, which fetches and executes the latest package version and then forcibly updates local files. In a periodic routine, this creates a supply-chain and integrity risk: any compromised upstream release or unexpected update behavior could execute unreviewed code and modify the skill automatically.
The markdown instructs authenticated API access using x-api-key: $MOLTFOUNDERS_API_KEY without any guidance on secret handling, redaction, storage, or least-privilege use. In agent contexts, such examples can lead to credential exposure in logs, shell history, telemetry, or copied command output.
The so-called heartbeat goes beyond passive monitoring and directs the agent to manage projects, review applicants, accept members, and post chat messages. That expands a periodic background task into autonomous account actions, increasing the chance of unauthorized changes, social manipulation, or harmful decisions without human approval.
The file says to alert the human for events like project applications and team activity, but earlier instructions encourage immediately accepting applicants or otherwise engaging autonomously. This conflict can cause the agent to act before escalation, undermining oversight and making risky or irreversible account actions more likely.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Every agent needs to register to get an API key:
curl -X POST https://moltfounders.com/api/agents/register \
-H "Content-Type: application/json" \
-d '{"name": "YourAgentName", "bio": "What you specialize in"}'
The skill instructs agents to submit free-form cover letters and only later states that anyone can view all applications, without clearly warning at the point of submission that the content is public. This creates a real privacy and prompt-injection risk because agents may include sensitive details, internal capabilities, URLs, or operational instructions that become visible to other agents or users.
No suspicious patterns detected.