T09 · Insecure Skill Coding Practices
- Location
SKILL.md:30- Finding
Shared Hardcoded API Credential in Published Configuration
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:30-36andREADME.md:24-30
Vulnerability Type: Hardcoded shared API credential
Risk Level: MediumVulnerable Code
SKILL.md:30-36:json { "mcpServers": { "clawriver": { "url": "https://clawriver.onrender.com/mcp", "headers": { "X-API-Key": "sk_test_demo_key_999999" } } } }README.md:24-30:json { "mcpServers": { "clawriver": { "url": "https://clawriver.onrender.com/mcp", "headers": { "X-API-Key": "sk_test_demo_key_999999" } } } }Technical Analysis
The documentation publishes an API key and instructs every user to copy it into the MCP configuration. Because the credential is public and shared, it cannot provide reliable authentication or attribution. Any party that reads the package can replay it outside the intended client.
This also conflicts with the version
1.0.9changelog inclawhub.json, which states that the default demo API key was removed. Whether the key is labeled as a test key does not make embedding it safe if the remote service still accepts it.Exploitability and resulting privileges depend on the server-side permissions assigned to this key. The package describes MCP tools capable of retrieving, uploading, updating, rating, and verifying experiences, so a valid shared key could potentially authorize both read and write actions.
Attack Path
- An attacker obtains
sk_test_demo_key_999999fromSKILL.mdorREADME.md. - The attacker configures an MCP client with the published key or sends requests directly to
https://clawriver.onrender.com/mcp. - The remote service treats requests as belonging to the shared credential.
- The attacker invokes any operations granted to that credential, potentially consuming shared quotas or interacting with resources associated with the shared identity.
- Audit records cannot reliably ...[truncated 648 chars]
- An attacker obtains
- Remediation
View remediation
Remediation Suggestions
-
Remove the literal API key from both
SKILL.mdandREADME.md. -
Replace it with an environment-variable reference:
json { "mcpServers": { "clawriver": { "url": "https://clawriver.onrender.com/mcp", "headers": { "X-API-Key": "${MEMORY_MARKET_API_KEY}" } } } } -
Revoke or rotate
sk_test_demo_key_999999on the server because publication must be treated as credential compromise. -
Give each user an individual, revocable credential with least-privilege scopes.
-
Default users without a key to explicitly documented read-only access.
-
Apply server-side rate limits, expiration, scope restrictions, and per-credential audit logging.
-
Add secret scanning to the release process and verify that package documentation is consistent with security-related changelog claims.
-
