Security audit

boc init

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent BOC deployment initializer, but it asks for privileged SSH access and includes destructive/system-changing steps without enough safety guidance.

Use this only for an intended BOC deployment machine. Confirm the SSH host, deploy directory, and package name before running anything; prefer SSH keys or temporary credentials over a plaintext root password; avoid putting passwords in chat or logs; back up or rename any existing BOC_k8s_noarch directory before deletion; and do not install the suggested sshpass binary unless you verify and trust the source.

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (5)

Context-Inappropriate Capability

Medium

Confidence: 94% confidence
Finding: The skill documentation expands scope beyond deployment initialization by directing users to install unrelated local tooling and download external binaries such as sshpass from GitHub. This increases supply-chain and host-compromise risk because operators may fetch and run unverified software on their local machine to satisfy the skill, even though those steps are not intrinsic to the platform initialization task.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The README instructs users to supply an SSH password for automated initialization but provides no guidance on secure handling, storage, masking, or transmission of that credential. In a deployment tool context, this increases the risk of password exposure through logs, shell history, chat transcripts, or insecure parameter passing, which could compromise privileged access to the target host.

Missing User Warnings

Low

Confidence: 78% confidence
Finding: The README describes automated extraction and execution of initialization steps that modify the deployment machine, but does not clearly warn users that the skill performs system-changing operations. In an infrastructure deployment context, omission of this warning can lead to unsafe use on the wrong host, accidental overwrites, or running untrusted packages with elevated privileges.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The skill instructs deletion of an existing directory with `rm -rf BOC_k8s_noarch` before extraction, but provides no explicit confirmation step, backup guidance, or warning that data may be destroyed. In an administrative SSH context, this can irreversibly delete a valid installation or operator data if the path is wrong, the working directory is not what is expected, or the directory contains important state.

Missing User Warnings

Medium

Confidence: 92% confidence
Finding: The skill requests SSH credentials including a plaintext password without any warning about secret handling, storage, logging, or safer authentication alternatives. In a remote administrative workflow, this raises the chance that sensitive credentials are exposed in prompts, transcripts, logs, or reused unsafely across systems.

Static analysis

No suspicious patterns detected.