T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:229- Finding
Over-Privileged System Modification and Persistent Service Enablement
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a plausible AI endpoint security runbook, but it asks for sensitive infrastructure details and recommends broad root-level host changes without enough guardrails.
Install only if you want an AI endpoint security runbook that may lead to administrator-level remediation. Do not let an agent execute the commands automatically; review each sudo, package upgrade, restart, firewall, audit, and fail2ban action first. Share only endpoint details you are comfortable exposing, prefer first-party cloud inventory over public IP-discovery services, redact secret-scan output, and pin container images or package versions before use.
SKILL.md:229Over-Privileged System Modification and Persistent Service Enablement
SKILL.md:276Overly Broad Privileged Host Reconnaissance and Secret Discovery
SKILL.md:42Public IP Disclosure to Third-Party Discovery Services
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
grep -r "password\|secret\|api_key\|token" ./config/ --include="*.json" --include="*.env" --include="*.yaml"
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
| CVE Range | Component | Action |
|---|---|---|
| CVE-2024-6387, CVE-2023-38408 | OpenSSH | `sudo apt update && sudo apt upgrade openssh-server` |
| CVE-2023-48795, CVE-2025-26465 | SSH protocol | Disable weak algorithms in `/etc/ssh/sshd_config` |
| CVE-2023-44487 | HTTP/2 (Rapid Reset) | Update nginx/apache, enable rate limiting |
| CVE-2022-* Apache series | Apache httpd | `sudo apt upgrade apache2` |
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
| CVE Range | Component | Action |
|---|---|---|
| CVE-2024-6387, CVE-2023-38408 | OpenSSH | `sudo apt update && sudo apt upgrade openssh-server` |
| CVE-2023-48795, CVE-2025-26465 | SSH protocol | Disable weak algorithms in `/etc/ssh/sshd_config` |
| CVE-2023-44487 | HTTP/2 (Rapid Reset) | Update nginx/apache, enable rate limiting |
| CVE-2022-* Apache series | Apache httpd | `sudo apt upgrade apache2` |
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
| CVE Range | Component | Action |
|---|---|---|
| CVE-2024-6387, CVE-2023-38408 | OpenSSH | `sudo apt update && sudo apt upgrade openssh-server` |
| CVE-2023-48795, CVE-2025-26465 | SSH protocol | Disable weak algorithms in `/etc/ssh/sshd_config` |
| CVE-2023-44487 | HTTP/2 (Rapid Reset) | Update nginx/apache, enable rate limiting |
| CVE-2022-* Apache series | Apache httpd | `sudo apt upgrade apache2` |
The trigger list includes broad phrases like 'security audit' and 'check my endpoint', which can cause unintended activation in unrelated conversations. In a skill that solicits infrastructure details and provides high-impact administrative commands, overbroad invocation increases the chance of accidental data disclosure or unsafe operational guidance being surfaced without clear user intent.
The skill explicitly asks users for sensitive infrastructure data including public IPs, hostnames, cloud provider, region, ASN, and deployment timing, but provides no privacy warning, minimization guidance, or handling constraints. This creates unnecessary exposure of high-value targeting information and could normalize sharing sensitive operational details into an AI workflow.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Using firewall (ufw):
# Block public access to port 18789
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
sudo ufw allow from <vpn-subnet> to any port 18789
sudo ufw reload
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
sudo ufw allow from <vpn-subnet> to any port 18789
sudo ufw reload
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
sudo ufw allow from <vpn-subnet> to any port 18789
sudo ufw reload
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
sudo ufw allow from <vpn-subnet> to any port 18789
sudo ufw reload
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo ufw deny 18789
# Allow only specific trusted IPs
sudo ufw allow from <your-office-ip> to any port 18789
sudo ufw allow from <vpn-subnet> to any port 18789
sudo ufw reload
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# Enable auditd
sudo apt install auditd -y
sudo systemctl enable --now auditd
# Log all authentication events
sudo auditctl -w /var/log/auth.log -p rwa -k auth_monitor
No suspicious patterns detected.