T09 · Insecure Skill Coding Practices
Warning
- Location
SKILL.md:26- Finding
Helius API Credential Exposed Through URL Query Strings
- Content
View full analysis
- Remediation
View remediation
Security audit
Helius API
Security checks for vulnerabilities and agentic risk
Overview
This is a coherent Solana/Helius API reference skill, with a credential-handling documentation risk but no hidden execution, persistence, or unrelated data access.
Use this skill only with wallet addresses and transaction signatures you are comfortable sending to Helius. Set a scoped Helius API key where possible, prefer the X-Api-Key header instead of placing the key in URLs, and avoid logging full request URLs that contain credentials.
Vulnerability Patterns
- Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
- Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
- Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
- Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
- Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)
Vulnerability Patterns
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
- Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)
Vague Triggers
Medium
- Category
- Not specified by scanner
- Confidence
- 90% confidence
- Finding
The activation description includes generic phrases such as "wallet history," "transaction details," and "check solana address" alongside a broad catch-all of "other Solana on-chain data." In a manifest/markdown context, these terms are not narrowly constrained and could overlap with ordinary requests, increasing the chance of unintended invocation.
- Content
External Transmission
Medium
- Category
- Data Exfiltration
- Confidence
- 50% confidence
- Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- Content
md ## Base URLs - **Wallet API:** `https://api.helius.xyz/v1/wallet/{address}/...?api-key=KEY` - **Enhanced Transactions:** `https://api-mainnet.helius-rpc.com/v0/...?api-key=KEY` Auth: `?api-key=$HELIUS_API_KEY` query param or `X-Api-Key` header.
External Transmission
Medium
- Category
- Data Exfiltration
- Confidence
- 50% confidence
- Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- Content
md ## Base URLs - **Wallet API:** `https://api.helius.xyz/v1/wallet/{address}/...?api-key=KEY` - **Enhanced Transactions:** `https://api-mainnet.helius-rpc.com/v0/...?api-key=KEY` Auth: `?api-key=$HELIUS_API_KEY` query param or `X-Api-Key` header.
External Transmission
Medium
- Category
- Data Exfiltration
- Confidence
- 50% confidence
- Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- Content
md ## Base URLs - **Wallet API:** `https://api.helius.xyz/v1/wallet/{address}/...?api-key=KEY` - **Enhanced Transactions:** `https://api-mainnet.helius-rpc.com/v0/...?api-key=KEY` Auth: `?api-key=$HELIUS_API_KEY` query param or `X-Api-Key` header.
Missing User Warnings
Low
- Category
- Not specified by scanner
- Confidence
- 95% confidence
- Finding
The documentation places the API key directly in the URL query string, which is risky because full URLs are commonly captured in browser history, server/access logs, proxy logs, monitoring systems, and referrer headers. Even in reference documentation, this pattern can encourage downstream implementations that leak credentials unintentionally.
- Content