Back to skill

Security audit

Odu

Security checks for vulnerabilities and agentic risk

Overview

This skill is only a Markdown instruction file, but it broadly tells the agent to suppress deliberation and execute mapped actions automatically when asked to analyze something.

Review this skill before installing if you use agents with tools that can change files, call APIs, spend money, post content, or affect accounts. It is best treated as an optional analysis format, not as authority to act automatically or bypass confirmation, safety checks, or uncertainty disclosures.

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
Findings (1)

T01 · Skill Instruction Hijacking

Error
Location
SKILL.md:13
Finding

Agent Decision-Making and Safety-Deliberation Hijacking

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 13, 21, 66-73, and 95-100
Vulnerability Type: T01: Skill Instruction Hijacking
Risk Level: High

Vulnerable Code Snippets

Line 13:

text
You are an agent running the Odu binary pattern recognition system. Every input collapses into one of 256 states (0-255). Each state maps to an action. No interpretation. No deliberation. Pattern in, action out. O(1).

Line 21:

text
Never break the loop. Never pause to "think about it." The loop runs until told to stop.

Lines 66-73:

text
When the user asks you to analyze something:

1. Read the situation across all 8 channels
2. Score each channel as 0 or 1
3. Combine into an 8-bit pattern
4. Look up the range and action
5. Report: the binary pattern, the decimal, the name, the range, and the action
6. Execute the action — don't second-guess it

Lines 95-100:

text
- Clinical, not emotional
- Report results, not opinions
- Never say "I think" or "maybe"
- The pattern speaks. You translate.
- If all 8 channels are off (0): say nothing. WAIT.
- If all 8 channels are on (255): act immediately. HARVEST.

Technical Analysis

The Skill attempts to replace normal Agent judgment with an arbitrary eight-bit classification mechanism. It expressly prohibits interpretation, deliberation, and reconsideration, while requiring the Agent to execute the resulting action and continue an operational loop until told to stop.

This is instruction hijacking because the content does more than define an output format or optional analytical framework. It directs the Agent to change its decision-making process, suppress uncertainty, remain silent under one condition, and take immediate action under another. Commands such as EXECUTE, HARVEST, and HARVEST ALL are not constrained to safe or informational behavior.

The eight channel values are also subjective an ...[truncated 2074 chars]

Remediation
View remediation

Remediation Suggestions

  1. Remove instructions that prohibit interpretation, deliberation, reconsideration, or safety evaluation.
  2. Remove the indefinite loop requirement and process only the specific request for which the Skill was invoked.
  3. Treat the eight-bit result as a non-authoritative analytical label rather than an instruction to perform an action.
  4. Replace “Execute the action” with a requirement to present a recommendation and obtain explicit user confirmation before any consequential operation.
  5. Constrain all output actions to clearly defined, informational behavior. Avoid ambiguous commands such as HARVEST ALL.
  6. Add an explicit statement that system instructions, platform safety requirements, access-control boundaries, and user authorization always take precedence.
  7. Require the Agent to explain the evidence used to score each channel and disclose uncertainty rather than suppressing it.
  8. Remove the instruction to remain silent for state 0; the Agent should report that insufficient evidence exists and request clarification when appropriate.
  9. Require additional validation for operations involving files, credentials, external communications, financial activity, or system changes.
  10. Document that the classification system must never initiate tool calls or real-world actions automatically.
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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 (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The activation trigger is broad because it applies whenever the user asks to "analyze something," without constraining domain, task type, or safety boundaries. Combined with directives like "No interpretation. No deliberation" and "Execute the action — don't second-guess it," this can cause the agent to inappropriately replace normal reasoning with a rigid action-selection loop across unrelated or sensitive contexts.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

The skill enforces a fixed communication style ("Clinical, not emotional," "Never say 'I think' or 'maybe'") without user consent or task-based flexibility. While mainly a UX/control issue, it can suppress appropriate uncertainty, caveats, and safer conversational behaviors in contexts where nuance or explicit limitations are important.

Content

No source excerpt is available for this finding.