TokenHawk — agentic threat model
TokenHawk is a low-risk, rule-based crypto alerting tool with minimal agentic capabilities, posing primarily data privacy and notification spoofing risks rather than autonomous execution threats.
OWASP AIVSS score rationale
| Autonomy of Action | 0.10 | |
| Goal-Driven Planning | 0.00 | |
| Self-Modification | 0.00 | |
| Dynamic Tool Use | 0.10 | |
| Persistent Memory | 0.10 | |
| Contextual Awareness | 0.10 | |
| Dynamic Identity | 0.00 | |
| Multi-Agent Interactions | 0.00 | |
| Non-Determinism | 0.10 | |
| Opacity & Reflexivity | 0.10 |
Scored with the canonical OWASP AIVSS formula (AIVSS calculator reference); agentic risk factors estimated from the agent’s described capabilities.
MAESTRO 7-layer threat model
Per-layer threats for this agent. Layers tagged “not certain from listing” are general, caveated commentary where the public description didn’t pin that layer.
Not certain from the listing — it is unclear if an LLM is utilized for natural language rule parsing or notification formatting. If a foundation model is present, it faces minor prompt injection risks that could alter notification content.
Not certain from the listing — data operations likely involve ingestion of public crypto price feeds and storage of user alert rules. Primary threats include price feed manipulation (oracle attacks) and unauthorized modification of user-defined thresholds.
Not certain from the listing — the system appears to use a standard deterministic rule engine rather than an agentic framework. If a framework is used, the lack of write-access tools limits the threat of malicious tool execution.
Not certain from the listing — infrastructure must securely host the alerting service and protect sensitive secrets such as Telegram bot tokens, email SMTP credentials, and user contact details from exposure.
Not certain from the listing — observability is critical to detect delayed price updates, rule evaluation failures, or notification delivery drops, which could lead to missed market signals for users.
Not certain from the listing — requires secure user authentication to prevent unauthorized modification of alert rules and compliance with data privacy regulations (e.g., GDPR) for storing user emails and Telegram handles.
The agent operates as a standalone utility with no multi-agent coordination or ecosystem integration described, resulting in zero ecosystem-specific threats.
MAESTRO — the 7-layer agentic threat-modeling framework (Cloud Security Alliance / Ken Huang).
These scores are auto-generated from public information (the agent's own listing, docs, and repository) using the canonical OWASP AIVSS formula and the MAESTRO framework — an estimate for guidance, not a penetration test, audit, or certification. See the scoring methodology — every score is re-derived by the same automated method as an agent's public evidence changes.