Back to skill

Security audit

Bom Manager

Security checks for vulnerabilities and agentic risk

Overview

This is a BOM spreadsheet workflow guide with no packaged executable code, network behavior, credential handling, or persistence.

Install only if you want the agent to help process BOM Excel files. Review outputs before using them for procurement or engineering decisions, and avoid providing sensitive BOMs unless you are comfortable with the agent reading those files for the requested task.

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
  • 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
88% confidence
Finding

The skill description uses broad activation language such as general BOM comparison, splitting, merging, and reporting tasks without clear boundaries, which can cause the agent to invoke this skill for ordinary spreadsheet or document requests that only loosely relate to BOM work. Over-broad routing increases the chance of unintended file access or execution of BOM-processing scripts in contexts where the user did not explicitly request this specialized behavior.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The trigger examples in the scenario table are short and generic, for example phrases equivalent to 'compare BOM', 'merge BOM', or 'generate change notes', with no negative constraints or disambiguation rules. In an agent environment, such generic triggers can capture unrelated enterprise workflows and cause inappropriate skill selection, leading to accidental processing of sensitive procurement or engineering files.

Content

No source excerpt is available for this finding.