Skills routeros-qemu-chr

📦

routeros-qemu-chr

Name: routeros-qemu-chr
Author: tikoci

Content revision r1 High Risk 🌐 Network access⚙️ External commands📁 Filesystem access

Run RouterOS CHR in QEMU

RouterOS CHR labs often fail because firmware, VirtIO, acceleration, and port forwarding differ by architecture. This skill provides tested QEMU patterns for local labs and CI workflows.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

This skill is part of a pack

Install the whole pack to get every skill the task needs, in one command.

TIKOCI RouterOS · 10 skills Install whole pack

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "routeros-qemu-chr" from https://skillstore.io/skills/tikoci-routeros-qemu-chr.md and its manifest at https://skillstore.io/api/skills/tikoci-routeros-qemu-chr/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/tikoci-routeros-qemu-chr.md Signed manifest GET /api/skills/tikoci-routeros-qemu-chr/manifest Signed lockfile GET /api/skills/tikoci-routeros-qemu-chr/lockfile

Test it

Using "routeros-qemu-chr". I need an x86_64 CHR lab on Linux with REST access.

Expected outcome:

The skill returns a launch plan using SeaBIOS, VirtIO disk and network, KVM when available, and localhost REST forwarding.

Using "routeros-qemu-chr". My aarch64 VM boots to a silent stall.

Expected outcome:

A diagnosis that checks UEFI pflash sizing and CPU model first.
A reminder to use explicit VirtIO PCI devices instead of the aarch64 shorthand.
A fallback plan for TCG when hardware acceleration is unavailable.

Using "routeros-qemu-chr". I need CI to test RouterOS package behavior.

Expected outcome:

The skill outlines image download, disk conversion, QEMU startup, readiness checks, package upload, reboot handling, and cleanup.

Security Audit

High Risk

v6 • 7/7/2026 Open versioned report

No prompt injection, hidden exfiltration, or malicious intent was found. The skill is legitimate RouterOS CHR and QEMU guidance, but it includes privileged host changes, external downloads, VM process launch, local service exposure, and predictable temp paths. These risks should be documented and gated by user confirmation before execution.

Files scanned

799

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (4)

High

references/github-actions-ci.md:46

World-Writable KVM Device Permission

The CI pattern writes a udev rule that sets the KVM device mode to 0666. This broadens virtualization access to every local user on shared or self-hosted runners.

The exact rule sets MODE="0666" for the KVM device. The impact is clear in shared runner or multi-user host contexts.

Medium

references/github-actions-ci.md:162

Network reconnaissance

sshpass -p '' scp -P 9122 -o StrictHostKeyChecking=no "$pkg" admin@127.0.0.1:/

The package upload uses sshpass with an empty admin password and disables host key checking against localhost. This is acceptable only for disposable local CHR instances.

Medium

references/chr-licensing.md:70 references/github-actions-ci.md:162-166

Default Empty RouterOS Administrator Credentials

Several examples use the default admin account with an empty password over SSH or HTTP. This is suitable only for disposable local CHR instances.

The examples show admin: or sshpass with an empty password. The context is local CI, but copying the pattern to persistent labs would be unsafe.

Medium

references/github-actions-ci.md:204-205

Destructive Git Cleanup Commands in CI Example

The retry pattern resets tracked files and removes untracked files before rebasing. This can delete local work if reused outside a disposable CI worktree.

The commands are explicitly present in the CI retry pattern. The documented context is CI, but the destructive behavior is real if copied elsewhere.

Capability review items (33)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

references/github-actions-ci.md:34

sudo privilege escalation

sudo apt-get update

The CI example runs apt with sudo, which modifies the host runner package state. This is legitimate setup work but requires elevated privileges.

High

references/github-actions-ci.md:35

sudo privilege escalation

sudo apt-get install -y qemu-system-x86 qemu-utils

The CI example runs apt with sudo, which modifies the host runner package state. This is legitimate setup work but requires elevated privileges.

High

references/github-actions-ci.md:46

sudo privilege escalation

echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' | sudo tee /etc/udev/rule

The CI example uses sudo to alter udev/KVM handling on the host. This broadens virtualization device access and is security-sensitive.

High

references/github-actions-ci.md:47

sudo privilege escalation

sudo udevadm control --reload-rules

The CI example uses sudo to alter udev/KVM handling on the host. This broadens virtualization device access and is security-sensitive.

High

references/github-actions-ci.md:48

sudo privilege escalation

sudo udevadm trigger --name-match=kvm

The CI example uses sudo to alter udev/KVM handling on the host. This broadens virtualization device access and is security-sensitive.

High

SKILL.md:97

Process spawn

const proc = Bun.spawn([

The skill shows Bun.spawn launching qemu-system-x86_64 with VM devices and forwarded ports. This is intended functionality, but it executes a host binary and starts a VM process.

Medium

references/chr-licensing.md:70

Hardcoded URL

curl -u admin: http://<router-ip>/rest/system/license

The example uses cleartext HTTP Basic auth to query a RouterOS license endpoint. This can expose credentials if copied outside a trusted local lab.

Medium

references/github-actions-ci.md:224

Shell command substitution

kill $(cat /tmp/qemu.pid) 2>/dev/null || true

The cleanup command reads a PID from a predictable temp file and passes it to kill. A tampered PID file could terminate an unintended process on less isolated hosts.

Medium

references/github-actions-ci.md:103

nohup (background persistent process)

nohup qemu-system-x86_64 \

The workflow backgrounds QEMU with nohup, creating a long-lived VM process. If cleanup fails, the process can persist and keep forwarded ports open.

Medium

references/github-actions-ci.md:166

Hardcoded URL

curl -sf -u admin: -X POST http://127.0.0.1:9180/rest/system/reboot || true

The workflow sends an authenticated reboot request using the default admin account with no password. This is safe only when the forwarded REST service is local and ephemeral.

Medium

references/github-actions-ci.md:162

Hardcoded IP address

sshpass -p '' scp -P 9122 -o StrictHostKeyChecking=no "$pkg" admin@127.0.0.1:/

The package upload uses sshpass with an empty admin password and disables host key checking against localhost. This is acceptable only for disposable local CHR instances.

Medium

references/github-actions-ci.md:166

Hardcoded IP address

curl -sf -u admin: -X POST http://127.0.0.1:9180/rest/system/reboot || true

The workflow sends an authenticated reboot request using the default admin account with no password. This is safe only when the forwarded REST service is local and ephemeral.

Medium

references/github-actions-ci.md:110

Temp directory access

> /tmp/qemu.log 2>&1 &

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

Medium

references/github-actions-ci.md:111

Temp directory access

echo $! > /tmp/qemu.pid

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

Medium

references/github-actions-ci.md:223

Temp directory access

if [ -f /tmp/qemu.pid ]; then

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

Medium

references/github-actions-ci.md:224

Temp directory access

kill $(cat /tmp/qemu.pid) 2>/dev/null || true

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

Medium

references/known-issues.md:55

nohup (background persistent process)

When backgrounding QEMU (e.g., `nohup qemu-system-x86_64 ... &`), use `exec` in the shell wrapper to

The reference discusses backgrounding QEMU with nohup. The surrounding text explains safe PID handling, but the pattern can still leave orphaned VMs if copied incorrectly.

Medium

references/known-issues.md:59

nohup (background persistent process)

nohup sh -c "qemu-system-x86_64 ..." &

The reference discusses backgrounding QEMU with nohup. The surrounding text explains safe PID handling, but the pattern can still leave orphaned VMs if copied incorrectly.

Medium

references/known-issues.md:62

nohup (background persistent process)

nohup sh -c "exec qemu-system-x86_64 ..." &

The reference discusses backgrounding QEMU with nohup. The surrounding text explains safe PID handling, but the pattern can still leave orphaned VMs if copied incorrectly.

Medium

references/known-issues.md:72

Temp directory access

socat -,rawer UNIX-CONNECT:/tmp/serial.sock,retry=10,interval=1

The example uses predictable /tmp paths for sockets or firmware variable files. This is operationally useful but can collide across users or VM instances.

Medium

references/known-issues.md:81

Temp directory access

VARS_COPY="/tmp/qemu-${VM_NAME}-vars.fd"

The example uses predictable /tmp paths for sockets or firmware variable files. This is operationally useful but can collide across users or VM instances.

Medium

SKILL.md:104

Temp directory access

"-chardev", `socket,id=serial0,path=/tmp/chr-serial.sock,server=on,wait=off`,

The programmatic QEMU example creates monitor or serial sockets under predictable /tmp paths. Shared hosts should use private per-instance directories and permissions.

Medium

SKILL.md:106

Temp directory access

"-monitor", `unix:/tmp/chr-monitor.sock,server,nowait`,

The programmatic QEMU example creates monitor or serial sockets under predictable /tmp paths. Shared hosts should use private per-instance directories and permissions.

Medium

SKILL.md:146

Temp directory access

cp /path/to/edk2-arm-vars.fd /tmp/my-vars.fd

The UEFI example copies writable firmware variables into /tmp. Predictable firmware-variable paths can collide or be clobbered on shared systems.

Medium

SKILL.md:150

Temp directory access

-drive if=pflash,format=raw,unit=1,file=/tmp/my-vars.fd \

The UEFI example copies writable firmware variables into /tmp. Predictable firmware-variable paths can collide or be clobbered on shared systems.

Low

references/github-actions-ci.md:71

Hardcoded URL

wget -q "https://download.mikrotik.com/routeros/${ROSVER}/chr-${ROSVER}.vdi.zip" \

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

Low

references/github-actions-ci.md:72

Hardcoded URL

|| wget -q "https://cdn.mikrotik.com/routeros/${ROSVER}/chr-${ROSVER}.vdi.zip"

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

Low

references/github-actions-ci.md:156

Hardcoded URL

wget -q "https://download.mikrotik.com/routeros/${ROSVER}/all_packages-x86-${ROSVER}.zip" \

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

Low

references/github-actions-ci.md:157

Hardcoded URL

|| wget -q "https://cdn.mikrotik.com/routeros/${ROSVER}/all_packages-x86-${ROSVER}.zip"

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

Low

SKILL.md:31

Fetch API call

const version = await fetch(

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

Low

SKILL.md:32

Hardcoded URL

`https://upgrade.mikrotik.com/routeros/NEWESTa7.${channel}`

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

Low

SKILL.md:36

Hardcoded URL

const url = `https://download.mikrotik.com/routeros/${version}/chr-${version}.img.zip`;

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

Low

SKILL.md:38

Hardcoded URL

const armUrl = `https://download.mikrotik.com/routeros/${version}/chr-${version}-arm64.img.zip`;

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

Risk Factors

🌐 Network access (20)

⚙️ External commands (92)

📁 Filesystem access (30)

Detected Patterns

Network reconnaissance

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/tikoci-routeros-qemu-chr/security.svg)](https://skillstore.io/skills/tikoci-routeros-qemu-chr?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/tikoci-routeros-qemu-chr?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/tikoci-routeros-qemu-chr/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/tikoci-routeros-qemu-chr.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

tikoci. (2026). routeros-qemu-chr security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6

BibTeX citation

@techreport{tikoci-tikoci-routeros-qemu-chr-2026,
  author = {tikoci},
  title = {routeros-qemu-chr security audit report (audit version 6)},
  institution = {Skillstore},
  year = {2026},
  number = {6},
  url = {https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "routeros-qemu-chr security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
  - name: "tikoci"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6"
identifiers:
  - type: other
    value: "skillstore:tikoci-routeros-qemu-chr:audit:6"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Build a Disposable RouterOS Lab

Create a local CHR VM for API testing, packet debugging, or training without hardware.

Add RouterOS Integration Tests

Run CHR in GitHub Actions to validate REST, packages, and generated schemas.

Diagnose CHR Boot Problems

Compare firmware, CPU, acceleration, and VirtIO choices when a VM stalls or times out.

Try These Prompts

Plan a CHR Lab

Plan a RouterOS CHR QEMU lab on my host. Ask for my host OS and CPU architecture if needed, then recommend the image, boot method, acceleration, RAM, disk, and port forwards.

Debug a Boot Failure

Diagnose this CHR boot failure: [symptoms]. Compare firmware, machine type, disk interface, CPU model, and VirtIO transport. Give a prioritized fix list.

Create a CI Workflow

Design a GitHub Actions workflow for a selected RouterOS CHR version. Include image download, disk conversion, QEMU startup, REST readiness checks, optional package upload, reboot handling, and safe cleanup.

Design a Multi-Arch Matrix

Build a multi-architecture CHR test strategy for x86_64 and aarch64 hosts. Include acceleration fallback rules, unsupported combinations, boot timing expectations, and skip logic.