Back to skill

Security audit

LLM Deploy Helper

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent local LLM deployment helper, but it needs Review because it can generate persistent root-level Docker services with network-exposed APIs and weak input and supply-chain safeguards.

Install only from a pinned release or commit, inspect generated docker-compose.yml or .service files before running them, bind services to localhost unless remote access is intentionally secured, protect any HF_TOKEN value, and avoid enabling the systemd service until you have reviewed persistence, root privileges, image provenance, and cleanup steps.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (4)

T09 · Insecure Skill Coding Practices

Error
Location
llm_deploy_helper/docker_templates.py:139
Finding

Unescaped model input permits deployment configuration injection

Content
View full analysis
/dev/null ExecStartPre=-/usr/bin/docker rm {svc}-server 2>/dev/null ExecStart={exec_line} ExecStop=/usr/bin/docker stop {svc}-server Restart=on-failure RestartSec=10 TimeoutStartSec=300 [Install] WantedBy=multi-user.target """) ``` ### Technical A ...[truncated 2497 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
llm_deploy_helper/docker_templates.py:145
Finding

Generated unauthenticated LLM APIs are exposed on all host interfaces

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Warning
Location
SKILL.md:22
Finding

Mutable installation sources and unpinned executable container images create supply-chain risk

Content
View full analysis
=8.0", "rich>=13.0", "pyyaml>=6.0", ] [project.optional-dependencies] full = ["psutil>=5.9"] ``` ### Technical Analysis The Git installation command does not select a commit hash or immutable release tag. Consequently, a future installation may retrieve source different from the audited artifact. The `latest` image tags can be reassigned to different image contents at any time. The `server` tag is also not an immutable digest. Generated configurations therefore execute whatever image those tags resolve to when pulled. Minimum-only Python dependency constraints permit future releases that were not part of this audit. This is less directly exploitable than a confirmed malicious dependency, but it weakens reproducibility and increases exposure to upstream compromise or malicious future ...[truncated 1370 chars]
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
llm_deploy_helper/docker_templates.py:257
Finding

Generated systemd units establish root-level persistence without least-privilege hardening

Content
View full analysis
/dev/null ExecStartPre=-/usr/bin/docker rm {svc}-server 2>/dev/null ExecStart={exec_line} ExecStop=/usr/bin/docker stop {svc}-server Restart=on-failure RestartSec=10 TimeoutStartSec=300 [Install] WantedBy=multi-user.target """) ``` The CLI instructs users to install and enable the unit system-wide: ```python console.print("[dim]Install with:[/dim]") console.print(f"[dim] sudo cp {output} /etc/systemd/system/[/dim]") console.print(f"[dim] sudo systemctl daemon-reload[/dim]") console.print(f"[dim] sudo systemctl enable --now {Path(output).stem}[/dim]") ``` The English documentation provides the same instructions: ```bash sudo cp ollama-llm.service /etc/systemd/system/ sudo systemctl daemon-reload sudo systemctl enable --now ollama-llm ``` ### Technical Analysis Generating a systemd service is part of the project's declared deployment functionality, and the user must explicitly run the displayed `sudo` commands. The persistence mechanism is therefore disclosed rather than hidden. However, installing the unit in `/etc/systemd/system/` and enabling it for `multi-user.target` causes it to survive the Skill invocation and start during future boots. The service has no `User=` or `Group=` directive, so a system-wide unit runs as root by default. It also lacks standard systemd sandboxing controls. The generated Docker command grants containers access to persistent v ...[truncated 1507 chars]
Remediation
View remediation
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Rogue AgentSelf-Modification, Session Persistence
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Findings (42)

External Model or Provider Selection

High
Category
Excessive Agency
Confidence
90% confidence
Finding

Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.

Content

Scanner excerpt · README.md (reported line 54)May include surrounding context.

bash
# Ollama (auto-uses GPU)
$ llm-deploy-helper generate --engine ollama --model llama3.1:8b

# vLLM (requires GPU)
$ llm-deploy-helper generate --engine vllm --model meta-llama/Llama-3.1-8B-Instruct

External Model or Provider Selection

High
Category
Excessive Agency
Confidence
90% confidence
Finding

Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.

Content

Scanner excerpt · README_EN.md (reported line 54)May include surrounding context.

bash
# Ollama (auto-uses GPU)
$ llm-deploy-helper generate --engine ollama --model llama3.1:8b

# vLLM (requires GPU)
$ llm-deploy-helper generate --engine vllm --model meta-llama/Llama-3.1-8B-Instruct

External Model or Provider Selection

High
Category
Excessive Agency
Confidence
90% confidence
Finding

Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.

Content

Scanner excerpt · README.md (reported line 60)May include surrounding context.

$ llm-deploy-helper generate --engine vllm --model meta-llama/Llama-3.1-8B-Instruct

llama.cpp (CPU/GPU)

$ llm-deploy-helper generate --engine llama.cpp --model llama3.1-8b-Q4_K_M.gguf --no-gpu --port 9090

text

Then start:

External Model or Provider Selection

High
Category
Excessive Agency
Confidence
90% confidence
Finding

Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.

Content

Scanner excerpt · README_EN.md (reported line 60)May include surrounding context.

$ llm-deploy-helper generate --engine vllm --model meta-llama/Llama-3.1-8B-Instruct

llama.cpp (CPU/GPU)

$ llm-deploy-helper generate --engine llama.cpp --model llama3.1-8b-Q4_K_M.gguf --no-gpu --port 9090

text

Then start:

External Model or Provider Selection

High
Category
Excessive Agency
Confidence
90% confidence
Finding

Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.

Content

Scanner excerpt · README.md (reported line 103)May include surrounding context.

3. Generate systemd service

bash
$ llm-deploy-helper systemd --engine ollama --model llama3.1:8b

Install:

External Model or Provider Selection

High
Category
Excessive Agency
Confidence
90% confidence
Finding

Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.

Content

Scanner excerpt · README_EN.md (reported line 72)May include surrounding context.

3. Generate systemd service

bash
$ llm-deploy-helper systemd --engine ollama --model llama3.1:8b

Install:

Tp4

High
Category
MCP Tool Poisoning
Confidence
90% confidence
Finding

Claiming hardware detection and simple local command generation while actually producing deployment templates and supporting additional infrastructure paths increases risk because it can introduce persistence or service exposure beyond a local setup helper. In agent contexts, this kind of understatement can bypass informed consent and lead to unintended configuration changes on the host.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

Claiming hardware detection and simple local command generation while actually producing deployment templates and supporting additional infrastructure paths increases risk because it can introduce persistence or service exposure beyond a local setup helper. In agent contexts, this kind of understatement can bypass informed consent and lead to unintended configuration changes on the host.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

Claiming hardware detection and simple local command generation while actually producing deployment templates and supporting additional infrastructure paths increases risk because it can introduce persistence or service exposure beyond a local setup helper. In agent contexts, this kind of understatement can bypass informed consent and lead to unintended configuration changes on the host.

Content

No source excerpt is available for this finding.

YARA rule 'agent_skill_remote_bootstrap_execution': Remote script or code download followed by execution/bootstrap installation [agent_skills]

High
Category
YARA Match
Confidence
94% confidence
Finding

The Quick Start instructs users to install directly from a GitHub repository using pip, which performs remote code retrieval and local package installation without the safety guarantees of a pinned, audited release artifact. In a skill context that already involves shell execution, this increases supply-chain risk and can result in arbitrary code running during installation or through package entry points.

Content

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

hat quantization? "Most annoyed I've ever been at myself for not going overboard with RAM" — r/LocalLLaMA (227↑). Everyone guesses wrong the first time.

The solution: One command detects your exact hardware, matches 15+ models against available RAM/VRAM, calculates utilization %, and spits out ready-to-run commands. No more downloading 50GB models that won't fit.

Quick Start

bash
pip install git+https://github.com/minirr890112-byte/llm-deploy-helper.git

llm-deploy              # default: chat scenario
llm-deploy coding       # coding-optimized models
llm-deploy reasoning    # reasoning-focused models

Real Output

text
$ llm-deploy coding

🖥 Hardware detected:
   OS: Darwin | CPU cores: 10
   RAM: 16 GB
   GPU: Apple Silicon (unified memory)

📋 Recommended models for 'coding':

⭐ #1   Qwen2.5 7B              4.5G     8G    28%
   #2   Llama 3.1 8B            5.0G    12G    31%
   #3   Gemma 3 12B             7.0G    16G    44%

🚀 Quick setup for Qwen2

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The README instructs users to copy a generated unit into /etc/systemd/system and enable it immediately with sudo, which installs a persistent system-level service. Even if the tool is legitimate, presenting these commands without a clear warning about persistence, privilege requirements, and the need to inspect the generated service file can lead users to run long-lived privileged software they do not fully understand.

Content

No source excerpt is available for this finding.

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
90% confidence
Finding

The README instructs users to use sudo to copy a generated service file into a privileged system directory. Encouraging privileged installation of generated artifacts without emphasizing review expands the blast radius if the generated file is unsafe or later modified.

Content

Scanner excerpt · README.md (reported line 109)May include surrounding context.

输出 ollama-llm.service,安装方法:

bash
sudo cp ollama-llm.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now ollama-llm

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
84% confidence
Finding

Running systemctl daemon-reload with sudo is part of privileged service installation and contributes to activating unreviewed generated configuration at the system level. While common administratively, it is risky when documentation encourages immediate execution without review gates.

Content

Scanner excerpt · README.md (reported line 110)May include surrounding context.

bash
sudo cp ollama-llm.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now ollama-llm

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
94% confidence
Finding

sudo systemctl enable --now creates persistence and starts the service immediately as a system-managed unit. This is dangerous because it both launches software and ensures it survives reboots, increasing impact if the generated service or underlying container configuration is insecure.

Content

Scanner excerpt · README.md (reported line 111)May include surrounding context.

bash
sudo cp ollama-llm.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now ollama-llm

4. 查看推荐模型列表

Session Persistence

Medium
Category
Rogue Agent
Confidence
95% confidence
Finding

The command systemctl enable --now establishes session persistence by registering the service to start automatically on boot and launching it immediately. In the context of a tool that generates service files, this increases risk because users may persistently deploy network-facing model-serving infrastructure without understanding exposure, resource usage, or service contents.

Content

Scanner excerpt · README.md (reported line 111)May include surrounding context.

bash
sudo cp ollama-llm.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now ollama-llm

4. 查看推荐模型列表

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The README instructs users to copy a generated service file into /etc/systemd/system and enable it with sudo, but it does not include any warning to inspect the generated unit first or explain the security implications of installing a persistent privileged service. This increases the chance that users will blindly deploy a service with broad host access and automatic startup, especially in a tool that generates configuration artifacts.

Content

No source excerpt is available for this finding.

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
95% confidence
Finding

The README tells users to run sudo cp to place a generated service into a system-wide unit directory, which is a privileged operation affecting host startup behavior. If the generated file is unsafe, tampered with, or overly permissive, this step helps install it with root-trusted persistence.

Content

Scanner excerpt · README_EN.md (reported line 78)May include surrounding context.

Install:

bash
sudo cp ollama-llm.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now ollama-llm

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
90% confidence
Finding

Running systemctl daemon-reload with sudo applies newly installed unit definitions at the system level, legitimizing any unsafe unit content previously copied into place. In isolation it is administrative boilerplate, but in this workflow it is part of installing persistent privileged configuration without a review warning.

Content

Scanner excerpt · README_EN.md (reported line 79)May include surrounding context.

bash
sudo cp ollama-llm.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now ollama-llm

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
97% confidence
Finding

sudo systemctl enable --now installs immediate execution plus persistence across reboots for the generated service. In a deployment helper that can generate service definitions, this is dangerous without strong warnings because it causes long-lived host-level execution of whatever command, container, ports, mounts, or environment the generated unit specifies.

Content

Scanner excerpt · README_EN.md (reported line 80)May include surrounding context.

bash
sudo cp ollama-llm.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now ollama-llm

4. List recommended models

Session Persistence

Medium
Category
Rogue Agent
Confidence
96% confidence
Finding

The use of systemctl enable creates session persistence by making the generated service start automatically on boot. Persistence meaningfully increases impact because any unsafe service behavior becomes durable and harder for users to notice or roll back, especially when combined with privileged installation steps.

Content

Scanner excerpt · README_EN.md (reported line 80)May include surrounding context.

bash
sudo cp ollama-llm.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now ollama-llm

4. List recommended models

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
79% confidence
Finding

The skill advertises behavior that inherently requires shell execution and potentially writing files, but it does not declare any tool scope or permissions boundaries. In an agent environment, missing scope declarations can lead to overbroad execution or make reviewers unaware that the skill may invoke local commands and create artifacts on disk.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The manifest describes a tool that detects hardware and outputs a ready local LLM setup command, but this CLI also writes full deployment artifacts to disk, including docker-compose and systemd unit files. Creating persistent deployment configuration files is broader behavior than the stated 'get the perfect local LLM setup command in one line' scope.

Content

No source excerpt is available for this finding.

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · llm_deploy_helper/cli.py (reported line 186)May include surrounding context.

python
console.print(Panel(content, title="Preview", border_style="dim"))
    console.print()
    console.print("[dim]Install with:[/dim]")
    console.print(f"[dim]  sudo cp {output} /etc/systemd/system/[/dim]")
    console.print(f"[dim]  sudo systemctl daemon-reload[/dim]")
    console.print(f"[dim]  sudo systemctl enable --now {Path(output).stem}[/dim]")

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · llm_deploy_helper/cli.py (reported line 187)May include surrounding context.

python
console.print(Panel(content, title="Preview", border_style="dim"))
    console.print()
    console.print("[dim]Install with:[/dim]")
    console.print(f"[dim]  sudo cp {output} /etc/systemd/system/[/dim]")
    console.print(f"[dim]  sudo systemctl daemon-reload[/dim]")
    console.print(f"[dim]  sudo systemctl enable --now {Path(output).stem}[/dim]")

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · llm_deploy_helper/cli.py (reported line 188)May include surrounding context.

python
console.print(Panel(content, title="Preview", border_style="dim"))
    console.print()
    console.print("[dim]Install with:[/dim]")
    console.print(f"[dim]  sudo cp {output} /etc/systemd/system/[/dim]")
    console.print(f"[dim]  sudo systemctl daemon-reload[/dim]")
    console.print(f"[dim]  sudo systemctl enable --now {Path(output).stem}[/dim]")