mcpbeat

Threat Detection

borghei/threat-detection

> This skill should be used when the user asks to "analyze logs for threats", "detect suspicious activity", "scan for brute force attempts", "identify injection attacks", or "audit access patterns for anomalies".

6k tokens
context cost
the whole folder, loaded on every use
3
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
447
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/borghei/Claude-Skills --skill threat-detection

What comes with it

20 285 bytes besides the instruction
references/threat-indicators.md
scripts/threat_signal_analyzer.py

The instruction itself

15 sections, as written by the author

Threat Detection

> Category: Engineering

> Domain: Security Operations

Overview

The Threat Detection skill provides automated analysis of log files for suspicious patterns including brute force attacks, injection attempts, unusual access patterns, and privilege escalation indicators. It helps security teams triage log data and identify threats before they escalate.

Clarify First

Before analyzing logs, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] Log file & source type — auth / access / application logs to analyze (--file; the subject of detection)
  • [ ] Threat category — brute force / injection / access anomaly / privilege escalation (--category; focuses the scan)
  • [ ] Minimum severity — the reporting/alert threshold (--min-severity; changes which signals surface and any SIEM/CI gate)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start

# Analyze a log file for threat signals
python scripts/threat_signal_analyzer.py --file /var/log/auth.log

# Analyze with specific threat category
python scripts/threat_signal_analyzer.py --file access.log --category injection

# JSON output for SIEM integration
python scripts/threat_signal_analyzer.py --file auth.log --format json

# Set minimum severity
python scripts/threat_signal_analyzer.py --file access.log --min-severity high

Tools Overview

threat_signal_analyzer.py

Analyzes log files for suspicious activity patterns across multiple threat categories.

| Feature | Description |

|---------|-------------|

| Brute force detection | Identifies repeated failed login attempts from same source |

| Injection scanning | Detects SQL injection, XSS, command injection in requests |

| Access anomalies | Flags unusual access times, forbidden paths, admin probes |

| Privilege escalation | Detects sudo abuse, role changes, permission modifications |

| Rate analysis | Identifies request flooding and denial-of-service patterns |

| IP reputation | Flags known-bad patterns (scanners, bots, TOR indicators) |

Workflows

Log Analysis Workflow

  • Collect - Gather logs from auth, access, application sources
  • Analyze - Run threat_signal_analyzer.py across log files
  • Triage - Review critical and high severity findings first
  • Correlate - Cross-reference findings across log sources
  • Respond - Block IPs, reset credentials, escalate as needed

Incident Investigation Workflow

  • Scope - Identify time window and affected systems
  • Scan - Run analyzer on all relevant log files
  • Timeline - Build timeline from threat signals
  • Impact - Assess what was accessed or modified
  • Contain - Block threat actors and patch vulnerabilities

Continuous Monitoring

# Cron job: analyze auth logs every hour
python scripts/threat_signal_analyzer.py --file /var/log/auth.log --format json --min-severity high > /tmp/threat_report.json

# CI/CD: scan application logs on deployment
python scripts/threat_signal_analyzer.py --file app.log --category injection --format json

Reference Documentation

  • Threat Indicators - Common attack patterns, indicators of compromise, response playbooks

Common Patterns Quick Reference

Threat Categories

| Category | Signals | Severity |

|----------|---------|----------|

| Brute force | 5+ failed logins from same IP in 5 min | High |

| SQL injection | UNION SELECT, OR 1=1, DROP TABLE in requests | Critical |

| XSS | script tags, javascript: URIs, event handlers in input | High |

| Path traversal | ../ sequences, /etc/passwd access attempts | High |

| Command injection | ; cat /etc/passwd, | nc, backtick usage | Critical |

| Admin probing | /admin, /wp-admin, /phpmyadmin access attempts | Medium |

| Rate flooding | 100+ requests/minute from single IP | High |

Severity Levels

  • CRITICAL - Active exploitation attempt (injection, RCE)
  • HIGH - Likely attack in progress (brute force, privilege escalation)
  • MEDIUM - Suspicious activity requiring investigation
  • LOW - Informational, possible false positive

Response Actions

| Severity | Immediate Action | Follow-Up |

|----------|-----------------|-----------|

| Critical | Block IP, alert SOC | Incident report, forensics |

| High | Rate limit, monitor | Review access, check damage |

| Medium | Log and monitor | Weekly review |

| Low | Log only | Monthly trend analysis |

How to use it

Copy the folder

Take borghei/threat-detection from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.