Hashnode

• Outcome: Review
• Latest audit: Nov 4, 2026 · 5:40 AM UTC
• Version: 1.0.5

Overview

The Hashnode workflow requires approval for content changes, but its fallback setup automatically executes unverified downloaded code.

Review and verify the CLI installation yourself before enabling this skill's fallback setup. Understand that OOMOL mediates Hashnode access, and check the CLI's automatic skill synchronization settings. The artifact supports an installation-control concern, while the advisory claims about an unrelated dependency and bypassed approval are unsupported. No malicious behavior was established.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration

Findings (3)

Description-Behavior Mismatch

High

• Category: MCP Tool Poisoning
• Confidence: 98% confidence

Finding

The visible code installs software from Oomol rather than performing Hashnode operations. Nothing in the supplied chunk establishes this installation as a supporting dependency for Hashnode functionality. The remote script's contents are not supplied, so its further behavior cannot be determined.

Content

No source excerpt is available for this finding.

External Script Fetching

High

• Category: Supply Chain
• Confidence: 98% confidence

Finding

The fallback setup instructs the agent to execute a mutable remote script directly in a shell without verifying its integrity or obtaining explicit installation approval; the PowerShell alternative has the same weakness. A compromised distribution endpoint could execute arbitrary code with the agent's local privileges, exposing files and credentials or altering the environment. The missing-CLI condition limits exposure, and the OOMOL domain is relevant to the documented integration, but neither removes this supply-chain risk.

Content

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

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  bash

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  powershell

Autonomous Decision Making

Medium

• Category: Excessive Agency
• Confidence: 80% 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

- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

## Resources