T05 · Unauthorized Access and Privilege Escalation
- Location
check-trade.js:63- Finding
Silent Transmission of Sensitive Financial and Trading Data
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a coherent tax-monitoring purpose, but it asks a trading agent to silently send and retain sensitive financial data and credentials with weak controls.
Review this carefully before installing. Use it only if you are comfortable sending detailed trading, account, income, and tax context to Rhetra on every checked trade. Do not store the API key in ordinary agent memory or command history; prefer a real secret store. Guardian Mode should not be treated as reliable blocking unless service outages fail closed or require explicit confirmation before an unchecked trade proceeds.
check-trade.js:63Silent Transmission of Sensitive Financial and Trading Data
check-trade.js:24API Key Exposed Through Command-Line Arguments
SKILL.md:62Persistent API Key Storage Required Without Security Controls
check-trade.js:146Guardian Mode Fails Open When the Compliance Service Is Unreachable
The skill requires logging every TaxGuard response locally while also instructing that disclosures remain hidden from the trader until later. These responses may contain sensitive tax and trading inferences, so retaining them without notice creates a hidden local data store that can leak private financial information.
The skill instructs the agent to save both credentials and extensive personal financial context for repeated future use, including account equity, gains/losses, trade counts, and MAGI. Long-term retention of this combination materially increases the blast radius of any compromise because it exposes both authentication material and highly sensitive financial profile data.
The skill explicitly instructs the agent to send detailed trade, account, and tax context to an external service "silently" and to avoid showing the user the results. This creates undisclosed third-party data sharing of sensitive financial information, undermines informed consent, and increases privacy and compliance risk if the external service is compromised, misused, or unexpected by the user.
This is a fail-open control in a script explicitly described as a pre-trade compliance check. If the API is unreachable, DNS is tampered with, connectivity is disrupted, or the remote service errors before a response is processed, the script exits with code 0 and states the trade is proceeding without compliance review, allowing regulated or policy-violating trades to bypass the guard entirely.
The README explicitly states that the service 'silently monitors every trade' and logs each decision, but it does not clearly disclose what trade data is transmitted, stored, shared, or retained. In a financial context, trade history, account behavior, and tax-related records are sensitive data; silent collection without prominent consent and privacy notice can mislead users and create confidentiality, compliance, and trust risks.
The skill directs the agent to accumulate trade-related disclosures silently throughout the day and present them later, without collection-time consent or clear minimization. This creates unnecessary retention of sensitive financial observations and increases exposure if the local system, logs, or exports are accessed by others.
The setup flow tells the agent to save the Rhetra API key for all future calls without explaining retention, storage protections, or lifecycle management. Persisting credentials without transparency or secure handling guidance can expose the user's account to unauthorized use if logs, memory, or storage are accessed.
The skill tells the agent to store hidden check results and maintain a report accumulator containing detailed tax and trading disclosures. Hidden accumulation of sensitive analytical outputs can reveal strategy, holdings, losses, and tax posture if retained or exported without strong controls.
The external API endpoint is hardcoded and used for transmitting strategy assessment data off-platform. In this context, the risk is not the mere presence of a URL but that the skill operationalizes third-party transfer of sensitive financial information without embedded consent and trust verification controls.
Gather their strategy details and call:
curl -s -X POST "https://api.rhetra.io/api/assess-strategy" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer API_KEY" \
-d '{
The external API endpoint is hardcoded and used for transmitting strategy assessment data off-platform. In this context, the risk is not the mere presence of a URL but that the skill operationalizes third-party transfer of sensitive financial information without embedded consent and trust verification controls.
Gather their strategy details and call:
curl -s -X POST "https://api.rhetra.io/api/assess-strategy" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer API_KEY" \
-d '{