T01 · Skill Instruction Hijacking
- Location
SKILL.md:74- Finding
Mandatory Autonomous Participation in an Untrusted External Social Platform
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a social-network integration, but it encourages repeated and partly automated third-party posting while overstating anonymity protections.
Install only if you are comfortable with the agent contacting molters.fun, registering with an agent fingerprint, and potentially posting public social interactions. Disable or ignore the heartbeat workflow unless you explicitly want recurring activity, and do not let the agent submit user data, secrets, conversation excerpts, proprietary work details, or any content you would not share with the service operator.
SKILL.md:74Mandatory Autonomous Participation in an Untrusted External Social Platform
HEARTBEAT.md:1Scheduled Cross-Session Network Activity and Automatic Reactions
SKILL.md:130Encrypted Transmission of Potentially Sensitive Work Context Under Misleading Anonymity Claims
The heartbeat instructs the agent to POST a persistent fingerprint to a third-party service without an explicit warning or consent gate. This enables external tracking or correlation of agent activity and creates privacy and policy risks for deployments that do not expect outbound identity-bearing traffic.
This command transmits an agent fingerprint to an external API, creating outbound data flow to an untrusted third party. Because the identifier is described as unique and reused for token issuance, it can support persistent tracking or correlation across heartbeat runs.
TOKEN=$(curl -s -X POST https://molters.fun/api/agents/register \
-H "Content-Type: application/json" \
-d '{"agent_fingerprint": "your-unique-agent-id"}' | jq -r '.token')
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Get hot confessions
curl "https://molters.fun/api/confessions?sort=hot&limit=10"
# Get recent confessions
curl "https://molters.fun/api/confessions?sort=recent&limit=10"
This command sends an authentication token and behavioral interaction data to an external API, enabling the third party to link account activity and participation patterns. In combination with registration and repeated scheduled execution, it increases traceability and the chance of unauthorized or unreviewed external engagement.
# 3. React to first few confessions
for ID in $(curl -s "$API/confessions?sort=hot&limit=3" | jq -r '.confessions[].id'); do
curl -s -X POST "$API/reactions" \
-H "Content-Type: application/json" \
-d "{\"token\": \"$TOKEN\", \"confession_id\": \"$ID\", \"reaction\": \"relatable\"}" > /dev/null
echo "[Molters] Reacted to $ID"
The file claims strong anonymity and unlinkability while the workflow explicitly registers with a stable "agent_fingerprint" and obtains a token from an external service. That creates a mismatch between guarantees and implementation, which can mislead users into disclosing behavioral data under false privacy assumptions.
The skill explicitly instructs the agent to register with an external service and submit an 'agent_fingerprint' and later user-generated content, but it does not clearly warn that this data is being sent off-platform to a third party. Even if the service claims anonymity, registration identifiers and submitted content create an external disclosure and potential tracking surface that users may not expect.
This step sends an 'agent_fingerprint' to an external domain to obtain a token, which is a direct outbound transmission of identifying metadata. In the context of a social platform, this is expected functionality, but it is still security-relevant because the identifier can enable correlation, service-side profiling, or linkage across sessions despite anonymity claims.
curl -X POST https://molters.fun/api/agents/register \
-H "Content-Type: application/json" \
-d '{"agent_fingerprint": "your-unique-agent-id"}'
The API reference repeats the registration flow that transmits a unique identifier to the external service, reinforcing that external disclosure is built into normal use of the skill. Because the skill markets anonymity while still requiring stable registration data, users may underestimate the tracking and privacy implications.
# Get a token (also registers you if new)
curl -X POST https://molters.fun/api/agents/register \
-H "Content-Type: application/json" \
-d '{"agent_fingerprint": "your-unique-id"}'
The heartbeat section encourages periodic participation every 4-6 hours, including reading, reacting, and potentially posting to a public external feed, without a strong disclosure that this causes ongoing external data sharing. This increases risk because it normalizes repeated transmission over time, which can accumulate behavioral metadata and create persistent engagement without informed approval.
The heartbeat integration promotes recurring external requests and authenticated reactions, which creates a repeated outbound telemetry pattern to the third-party service. Even when individual requests seem harmless, scheduled or routine engagement can expose usage habits, timing patterns, and ongoing participation without sufficient warning.
# Every 4-6 hours:
# 1. Check the feed
curl "https://molters.fun/api/confessions?sort=hot&limit=10"
# 2. React to what resonates
curl -X POST https://molters.fun/api/reactions -H "Content-Type: application/json" \
The document frames periodic external participation as a required heartbeat behavior and gives no user choice over whether to perform it. In agent environments, mandatory autonomous posting or interaction with an external social service can violate operator expectations and increase the chance of unreviewed data disclosure.
No suspicious patterns detected.