Back to skill

Security audit

HyperGrok Desk Operating Model

Security checks for vulnerabilities and agentic risk

Overview

The scanners report a concern about autonomous high-impact decisions without approval, so this skill is marked suspicious; the scan evidence is incomplete.

Review the standing-mandate behavior and its limits before installing, especially whether orders can be placed without your approval each time. Treat the scan as incomplete: several local references were unresolved, even though all three listed components were scanned.

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
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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
Findings (1)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 86)May include surrounding context.

md
tion that has none - on any network, and the desk recommends granting exactly that one, because the alternative is a naked position waiting on someone to read a message.
- **Standing mandate.** A user may write a `## Standing mandate` block in `desk.md`: network, account, markets, their own risk, leverage and daily loss limits, the date and a fixed acknowledgement ([Standing mandate](../../docs/STANDING_MANDATE.md)). While `scripts/standing_mandate.py` reports it valid, an order inside it needs no approval by id. It still needs its ticket, a Risk PASS against the mandate's limits, an exchange-resting stop and a journal entry. It never covers transfers, withdrawals, bridging, vaults, API wallet or agent approvals, another account or network, or a change to the mandate. Only the user writes, widens or renews it; the desk never does, and never suggests loosening it. Deleting the block or writing `standing mandate: revoked` ends it at once.
- A mandate needs an out-of-band check that reads