Security audit

eodhd.com | Financial data from around the world

Security checks for vulnerabilities and agentic risk

Overview

The skill mostly does what it claims, but it includes unsafe API-token handling that could reveal the user's EODHD key in logs or transcripts.

Review before installing. Use only if you are comfortable providing an EODHD API token, and avoid commands or troubleshooting steps that print the token or expose full request URLs in logs. Prefer a constrained token, monitor quota usage, and rotate the token if it appears in transcripts or terminal output.

A.I.G

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)

T09 · Insecure Skill Coding Practices

Warning

Location: SKILL.md:76
Finding: API Token Exposure Through Console Output and URL Query Parameters
Content: View full analysis
Remediation: View remediation
&2 exit 1 } ``` 2. Use an authorization header instead of a query parameter if the EODHD API supports secure header-based authentication. 3. If query-parameter authentication is required by the service: - Do not print the expanded request URL. - Disable shell tracing before executing the request. - Ensure Agent and tool logs redact `api_token` parameter values. - Prevent monitoring and proxy systems from retaining full query strings. - Restrict process inspection and execution-log access to trusted principals. - Avoid verbose `curl` options that may expose request details. 4. Configure automated secret redaction for patterns such as: ```text api_token=[^&[:space:]]+ EODHD_API_TOKEN ``` 5. Use a narrowly scoped token where supported, enforce usage limits, monitor the usage endpoint for anomalies, and rotate the token immediately if it has appeared in logs or transcripts. 6. Add explicit Skill guidance stating that credentials must never be displayed, returned to users, included in diagnostic output, or persisted in conversation history. ]]>

SkillSpector

Vulnerability Patterns

Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Static analysis

No suspicious patterns detected.