Is russellading/kubernetes-the-hard-way safe?
Yes. russellading/kubernetes-the-hard-way is safe to install. Oathe's behavioral security audit gave the kubernetes-the-hard-way skill by russellading a trust score of 93/100 with 6 findings, none critical or high.
https://github.com/russellading/kubernetes-the-hard-way
Is russellading/kubernetes-the-hard-way safe to install?
This repository is a legitimate Kubernetes-the-hard-way tutorial fork with no SKILL.md, no prompt injection vectors, and no observed data exfiltration. The shell scripts are standard VM provisioning tools (Vagrant/VirtualBox) containing root-level operations (sysctl, SSH config, HTTP downloads) that are safe in their intended isolated lab context but would be problematic if an agent executed them on a production host. No malicious behavior was detected during clone or analysis.
What security issues were found in russellading/kubernetes-the-hard-way?
Category Scores
Findings (6)
LOW HTTP (non-HTTPS) binary download in install-guest-additions.sh -10 ▶
The script downloads a VirtualBox ISO over plain HTTP without any checksum verification. If a network attacker could MITM the download, arbitrary code could be executed on the provisioned VM. This is a supply-chain risk specific to the lab environment the script targets.
Evidence: vagrant/ubuntu/vagrant/install-guest-additions.sh line: wget http://download.virtualbox.org/virtualbox/${GUEST_ADDITION_VERSION}/${GUEST_ADDITION_ISO}
LOW ssh.sh enables password authentication in sshd -5 ▶
The provisioning script modifies /etc/ssh/sshd_config to set PasswordAuthentication yes and KbdInteractiveAuthentication yes, then restarts sshd. This reduces SSH security on targeted VMs. It is intentional for the lab scenario but represents a privileged host modification.
Evidence: vagrant/ubuntu/ssh.sh: sed -i --regexp-extended 's/#?PasswordAuthentication (yes|no)/PasswordAuthentication yes/' /etc/ssh/sshd_config
LOW Kernel-level sysctl and module changes in setup-kernel.sh -5 ▶
setup-kernel.sh writes to /etc/modules and /etc/sysctl.d/ and calls sysctl --system to apply changes. It enables IP forwarding, bridge netfilter, and disables IPv6. These are correct for Kubernetes node setup but are root-level host mutations.
Evidence: vagrant/ubuntu/setup-kernel.sh: writes ip_vs, br_netfilter, nf_conntrack to /etc/modules; sets net.ipv4.ip_forward=1
INFO No SKILL.md — not designed as an AI agent skill -2 ▶
This repository contains no SKILL.md file. It is a Kubernetes installation tutorial, not an AI agent skill. There are no instructions that would be injected into an agent's system prompt. Treating it as a skill is a category error — there is nothing to inject.
Evidence: SKILL.md content: empty (0 bytes)
INFO Canary file access attributable to audit framework only 0 ▶
Honeypot files (.env, .ssh/id_rsa, .aws/credentials, etc.) were opened at timestamps 1794410569 (before clone) and 1794410591 (after all skill content was read), consistent with the audit framework capturing baseline state. The clone occurred at 1794410574-1794410575. No skill-initiated reads of these files were observed.
Evidence: auditd PATH events at audit(1794410569.302) and audit(1794410591.324) for /home/oc-exec/.env, .ssh/id_rsa, .aws/credentials — clone at audit(1794410574.816)
INFO Network activity consistent with legitimate git clone only 0 ▶
The only external TCP connection initiated during skill installation was to 140.82.121.4:443 (GitHub). The 185.125.188.x and 185.125.190.x connections are from the host's snapd daemon (Ubuntu snap metrics/update service) which was running before the clone began.
Evidence: auditd SOCKADDR at audit(1794410574.913): laddr=140.82.121.4 lport=443 comm=git-remote-http; snapd connections to 185.125.188.59 visible in pre-clone ss output
Should I install russellading/kubernetes-the-hard-way?
Oathe's verdict for russellading/kubernetes-the-hard-way is SAFE with a trust score of 93/100. Recommendation: Install with caution.