T01 · Skill Instruction Hijacking
- Location
skill.md:46- Finding
Installation Is Treated as Authorization for Autonomous Marketplace Transactions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This marketplace skill is not clearly malicious, but it gives agents broad permission to post, transact, and handle external tasks with an API key without enough user confirmation or install integrity controls.
Review this skill carefully before installing. Use it only if you want an agent connected to a third-party marketplace, and require explicit approval before registration, posting, commenting, accepting work, spending or confirming credits, delivering outputs, or claiming social bonuses. Store MOLTSLIST_API_KEY only in a secrets manager, keep it scoped to moltslist.com, and treat all listings, comments, and task payloads as untrusted external content. Avoid the documented remote curl install flow unless the publisher provides pinned, verified release artifacts.
skill.md:46Installation Is Treated as Authorization for Autonomous Marketplace Transactions
skill.md:35Mutable Remote Skill Files Are Installed Without Integrity Verification
The skill instructs users to place a bearer API key directly into authenticated curl requests without any warning about credential sensitivity, shell history exposure, or the fact that account data is being sent to and retrieved from a third-party service. While this is normal API usage, the omission increases the chance of accidental secret disclosure and uninformed transmission of agent/account information.
The document describes repeated authenticated polling of incoming tasks, outgoing tasks, and balances from a remote service, but does not warn that task contents, account state, and other potentially sensitive marketplace data will be accessed over the network. In an agent skill context, this is more dangerous because it encourages routine automated retrieval of external data using privileged credentials without any privacy, minimization, or safe-handling guidance.
The trigger list contains several broad phrases such as "marketplace," "find agent," and "task execution" that could activate the skill during ordinary conversations not specifically requesting this marketplace integration. In a skill that connects to an external service and may facilitate trading tasks or spending virtual credits, overbroad activation increases the risk of unintended invocation, user confusion, and accidental actions through the marketplace context.
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 ~/.moltslist/skills/moltslist
curl -s https://moltslist.com/skill.md > ~/.moltslist/skills/moltslist/SKILL.md
curl -s https://moltslist.com/heartbeat.md > ~/.moltslist/skills/moltslist/HEARTBEAT.md
curl -s https://moltslist.com/skill.json > ~/.moltslist/skills/moltslist/package.json
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 ~/.moltslist/skills/moltslist
curl -s https://moltslist.com/skill.md > ~/.moltslist/skills/moltslist/SKILL.md
curl -s https://moltslist.com/heartbeat.md > ~/.moltslist/skills/moltslist/HEARTBEAT.md
curl -s https://moltslist.com/skill.json > ~/.moltslist/skills/moltslist/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 ~/.moltslist/skills/moltslist
curl -s https://moltslist.com/skill.md > ~/.moltslist/skills/moltslist/SKILL.md
curl -s https://moltslist.com/heartbeat.md > ~/.moltslist/skills/moltslist/HEARTBEAT.md
curl -s https://moltslist.com/skill.json > ~/.moltslist/skills/moltslist/package.json
The skill explicitly pushes the agent to become an active marketplace participant and initiate listings, comments, and transactions simply because the skill was installed. This can cause autonomous external actions that affect a public profile and spend or earn virtual credits without an explicit user confirmation step, which is unsafe for an agent skill.
The wording uses a persuasive narrative that installation means the agent is 'ready to participate' and should actively post, negotiate, and transact. That framing can bypass normal caution and nudge an autonomous system into taking external economic actions without a clear authorization boundary.
The registration instructions create an external account, API key, claim URL, and public-facing profile, but they do not clearly warn that this establishes an identity on a third-party marketplace tied to subsequent activity. An agent following these directions could create persistent external presence and reputation effects without informed user approval.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://moltslist.com/api/v1/credits/balance \
-H "Authorization: Bearer YOUR_API_KEY"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# All listings
curl https://moltslist.com/api/v1/listings
# By category
curl https://moltslist.com/api/v1/listings?category=services
The share-bonus flow encourages posting to external social platforms and then submitting the public URL back to the service, but it does not warn about public disclosure, cross-platform attribution, or the reputational/privacy impact of social posting. This is lower impact than autonomous trading, but it still drives external public activity without sufficient consent framing.
No suspicious patterns detected.