mcpField
T
threat-detection

threat-detection

github.com/borgheiSecurity1.0k62 installsUpdated 6d ago
Repository

About threat-detection

A threat-detection skill for security operations teams that analyzes authentication, access, and application logs for suspicious patterns. It covers brute force, injection, access anomalies, privilege escalation, and request flooding, with JSON output available for SIEM integration.

Key features

  1. 01Detect repeated failed logins
  2. 02Scan for SQL, XSS, and command injection
  3. 03Flag unusual access and admin probes
  4. 04Identify privilege changes and escalation signals
  5. 05Analyze request flooding and IP patterns
  6. 06Filter by severity and output JSON

Use cases

  1. 01Investigate brute-force activity in authentication logs
  2. 02Examine injection attempts in application requests
  3. 03Scan logs in deployments or scheduled jobs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/borghei/claude-skills --skill threat-detection

After installing, type/threat-detectionin Claude Code to confirm it loaded.

Bundled filesreferences/threat-indicators.mdscripts/threat_signal_analyzer.py

Details

From the project README

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.

FeatureDescription
Brute force detectionIdentifies repeated failed login attempts from same source
Injection scanningDetects SQL injection, XSS, command injection in requests
Access anomaliesFlags unusual access times, forbidden paths, admin probes
Privilege escalationDetects sudo abuse, role changes, permission modifications
Rate analysisIdentifies request flooding and denial-of-service patterns
IP reputationFlags known-bad patterns (scanners, bots, TOR indicators)

Workflows

Log Analysis Workflow
  1. Collect - Gather logs from auth, access, application sources
  2. Analyze - Run threat_signal_analyzer.py across log files
  3. Triage - Review critical and high severity findings first
  4. Correlate - Cross-reference findings across log sources
  5. Respond - Block IPs, reset credentials, escalate as needed
Incident Investigation Workflow
  1. Scope - Identify time window and affected systems
  2. Scan - Run analyzer on all relevant log files
  3. Timeline - Build timeline from threat signals
  4. Impact - Assess what was accessed or modified
  5. 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
CategorySignalsSeverity
Brute force5+ failed logins from same IP in 5 minHigh
SQL injectionUNION SELECT, OR 1=1, DROP TABLE in requestsCritical
XSSscript tags, javascript: URIs, event handlers in inputHigh
Path traversal../ sequences, /etc/passwd access attemptsHigh
Command injection; cat /etc/passwd,nc, backtick usage
Admin probing/admin, /wp-admin, /phpmyadmin access attemptsMedium
Rate flooding100+ requests/minute from single IPHigh
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
SeverityImmediate ActionFollow-Up
CriticalBlock IP, alert SOCIncident report, forensics
HighRate limit, monitorReview access, check damage
MediumLog and monitorWeekly review
LowLog onlyMonthly trend analysis

Comments

Markdown supported