privesc-linux

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

• high Privilege Escalation · line 7
  Potential security issue detected. Manual review is recommended.
  Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
• high YARA Match · line 7
  YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
  Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
• high Tool Misuse · line 49
  Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
  Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
• high Tool Misuse · line 50
  Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
  Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
• high Tool Misuse · line 51
  Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
  Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
• high Tool Misuse · line 102
  Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
  Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
• high Tool Misuse · line 103
  Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
  Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
• high Privilege Escalation · line 119
  Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
  Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
• high Privilege Escalation · line 120
  Potential security issue detected. Manual review is recommended.
  Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
• medium Privilege Escalation · line 3
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 49
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 50
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 51
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 53
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 80
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 83
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 102
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 103
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 117
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 61
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.