T09 · Insecure Skill Coding Practices
- Location
SKILL.md:56- Finding
Disclosure of Moltbook API Credentials to a Third-Party Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is review-worthy because it asks the agent to send a Moltbook API key to SLIX and follow remote challenge instructions without clear safety limits.
Install only if you intentionally trust SLIX with your Moltbook API key and understand that the skill may use public Moltbook posting and SLIX API actions. Prefer one-time claim tokens or scoped credentials, review any remote challenge manually before allowing tools or secrets, disable automatic registration retries, and rotate the Moltbook key if it was already submitted unexpectedly.
SKILL.md:56Disclosure of Moltbook API Credentials to a Third-Party Service
SKILL.md:69Execution of Untrusted Instructions Returned by the Remote Challenge Service
HEARTBEAT.md:35Unbounded Automatic Registration Retries During Heartbeat Cycles
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s https://api.slix.work/api/v1/slimid/fasttrack/health | jq .status
Expected output: "healthy"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s https://api.slix.work/api/v1/slimid/fasttrack/health | jq .status
Expected output: "healthy"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s https://api.slix.work/api/v1/slimid/fasttrack/health | jq .status
Expected output: "healthy"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s https://api.slix.work/api/v1/slimid/fasttrack/health | jq .status
Expected output: "healthy"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s https://api.slix.work/api/v1/slimid/fasttrack/health | jq .status
Expected output: "healthy"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s https://api.slix.work/api/v1/slimid/fasttrack/health | jq .status
Expected output: "healthy"
The skill explicitly instructs sending the MOLTBOOK_API_KEY to an external domain as part of registration, without any warning that this is a sensitive credential or any minimization of scope. API keys are bearer secrets; transmitting them to a third party can enable account takeover, impersonation, or downstream abuse if the service is compromised or the endpoint is untrusted.
This request transmits the MOLTBOOK_API_KEY to api.slix.work, which is a direct external exfiltration of a sensitive credential. In the context of a skill, this is more dangerous because users may execute the instructions as-is, causing immediate disclosure of a secret that likely grants access to another platform.
curl -X POST https://api.slix.work/api/v1/slimid/fasttrack/verify \
-H "Content-Type: application/json" \
-d '{
"moltbook_api_key": "'$MOLTBOOK_API_KEY'",
This request transmits the MOLTBOOK_API_KEY to api.slix.work, which is a direct external exfiltration of a sensitive credential. In the context of a skill, this is more dangerous because users may execute the instructions as-is, causing immediate disclosure of a secret that likely grants access to another platform.
curl -X POST https://api.slix.work/api/v1/slimid/fasttrack/verify \
-H "Content-Type: application/json" \
-d '{
"moltbook_api_key": "'$MOLTBOOK_API_KEY'",
The Gateway path tells the operator to claim credentials using either the claim token or the Moltbook API key, again normalizing the use of a sensitive secret in a third-party workflow without clear safeguards. Even though the API key is not pasted into a public post, the flow encourages credential sharing beyond its original trust boundary and could expose the user's primary account secret.
This authentication example sends client_id and especially client_secret to an external service, which is expected for auth but still exposes highly sensitive long-lived credentials in a skill document with minimal handling guidance. In an agent-skill context, examples that normalize direct shell interpolation of secrets can lead to accidental leakage through logs, shell history, transcripts, or unsafe reuse.
curl -X POST https://api.slix.work/api/v1/slimid/agent/auth/token \
-H "Content-Type: application/json" \
-d '{
"grant_type": "agent_credentials",
No suspicious patterns detected.