Back to skill

Security audit

market-journal

Security checks for vulnerabilities and agentic risk

Overview

The scanners classify this skill as benign because its reported capabilities appear aligned with market forecasting and journaling, while noting permission and request-routing concerns; the review is incomplete.

The verdict is benign, with medium confidence, but the scan was partial: one of three components was fully inspected and tool-misuse analysis was degraded. Before installing, consider whether you are comfortable with the reported network capability and forecast default behavior; the declared permissions do not establish the host runtime's actual limits.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Code capability 'network' detected in scripts/forecast.mjs but not covered by declared permissions.

High
Category
MCP Least Privilege
Confidence
75% confidence
Finding

The skill uses 'network' capability that is not covered by the declared 'allowed-tools' preapproval. Review the host runtime's actual enforcement policy; runtime permissions are unknown unless separately verified, and this declaration alone does not establish a permission ceiling.

Content

No source excerpt is available for this finding.

Ambiguous requests default to the forecasting workflow instead of requiring a clear match.

Low
Category
Trigger Abuse
Confidence
94% confidence
Finding

The routing instructions select forecasts whenever the user mentions forecasts generally and explicitly default to forecasts when the request fits neither routine clearly. This does not distinguish prediction-market forecasting from unrelated forecasting requests and can initiate the workflow without clear user intent.

Content

No source excerpt is available for this finding.