Back to skill

Security audit

Slack Bot

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent Slack Bot connector, but its setup path asks for direct execution of remote installer scripts, which needs review before use.

Install only after reviewing the OOMOL CLI source and installer path, preferably using a pinned or verified method. Before connecting Slack, check the workspace scopes and require explicit confirmation for posts, uploads, updates, deletes, and reactions.

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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • 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
Findings (2)

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

The skill includes a curl ... | bash installation command that fetches and executes a remote script directly, which is a well-known supply-chain and remote code execution risk. If the install endpoint, transport, or upstream distribution is compromised, an agent or user following this instruction could execute attacker-controlled code on the host.

Content

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill description instructs the agent to use this skill for ANY Slack Bot request and instead of calling the API directly, which is an overly broad trigger that can cause unintended invocation across a wide range of Slack-related tasks. In an agentic environment, this increases the chance of the skill being selected for sensitive read, write, or destructive operations without sufficiently narrow scoping or contextual safeguards.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.