ClawHub
Back to skill

Security audit

Profitabul

Security checks for vulnerabilities and agentic risk

Overview

This skill is coherent, but it enables real trading actions without enough user-facing safeguards or warnings.

Install only if you intentionally want an agent connected to Profitabul and, if enabled, a live brokerage workflow. Keep the API key secret, avoid sharing it in chats or commits, rotate it if exposed, and use broker-side limits, paper trading, and explicit confirmations before allowing any live trade tools.

A.I.G

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill explicitly advertises live trade execution capabilities but does not include a clear warning that actions may place real-money orders with financial consequences. In an agent context, this is dangerous because users may treat tool calls as routine analysis steps and unintentionally authorize irreversible market activity or losses.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

The setup instructions tell users to store a live API key and show its prefix, but provide no warning about treating the key as a secret or avoiding logs, screenshots, commits, and prompt disclosure. Because the key appears to authorize market data and potentially live execution, leakage could enable unauthorized access or trading through the connected account.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.