detecting-rdp-brute-force-attacks

Detect RDP brute force attacks by analyzing Windows Security Event Logs for failed authentication patterns (Event ID 4625), successful logons after failures (Event ID 4624), NLA failures, and source IP frequency analysis.

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

8.6K

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/detecting-rdp-brute-force-attacks

0

installs

0

this week

8.6K

stars

Installation Guide

How to use detecting-rdp-brute-force-attacks on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add detecting-rdp-brute-force-attacks
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/detecting-rdp-brute-force-attacks

Fetches detecting-rdp-brute-force-attacks from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/detecting-rdp-brute-force-attacks

Restart Cursor to activate detecting-rdp-brute-force-attacks. Access via /detecting-rdp-brute-force-attacks in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

name
detecting-rdp-brute-force-attacks
description
Detect RDP brute force attacks by analyzing Windows Security Event Logs for failed authentication patterns (Event ID 4625), successful logons after failures (Event ID 4624), NLA failures, and source IP frequency analysis.
domain
cybersecurity
subdomain
threat-detection
tags
- threat-detection - rdp - brute-force - windows-event-logs - blue-team - siem
version
'1.0'
author
mahipal
license
Apache-2.0
nist_csf
- DE.CM-01 - DE.AE-02 - DE.AE-06 - ID.RA-05

Detecting RDP Brute Force Attacks

Overview

RDP brute force attacks target Windows Remote Desktop Protocol services by attempting rapid credential guessing against exposed RDP endpoints. Detection relies on analyzing Windows Security Event Logs for Event ID 4625 (failed logon with Logon Type 10 or 3) and correlating with Event ID 4624 (successful logon) to identify compromised accounts. This skill covers parsing EVTX files with python-evtx, identifying attack patterns through source IP frequency analysis, detecting NLA bypass attempts, and generating actionable detection reports.

When to Use

  • When investigating security incidents that require detecting rdp brute force attacks
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • Python 3.9+ with python-evtx, lxml libraries
  • Windows Security EVTX log files (exported from Event Viewer or collected via WEF)
  • Understanding of Windows authentication Event IDs (4624, 4625, 4776)
  • Familiarity with RDP Logon Types (Type 3 for NLA, Type 10 for RemoteInteractive)

Steps

Step 1: Export Security Event Logs

Export Windows Security logs to EVTX format using Event Viewer or wevtutil:

wevtutil epl Security C:\logs\security.evtx

Step 2: Parse Failed Logon Events

Use python-evtx to parse Event ID 4625 entries, extracting source IP, target username, failure reason (Sub Status), and Logon Type fields.

Step 3: Analyze Attack Patterns

Identify brute force patterns by:

  • Counting failed logons per source IP within time windows
  • Detecting username spray attacks (many usernames from one IP)
  • Correlating 4625 failures with subsequent 4624 success from same IP

Step 4: Generate Detection Report

Produce a JSON report with top attacking IPs, targeted accounts, time-based analysis, and compromise indicators.

Expected Output

JSON report containing:

  • Total failed logon events and unique source IPs
  • Top attacking IPs ranked by failure count
  • Targeted usernames and failure sub-status codes
  • Successful logons following brute force attempts (potential compromises)
  • Time-series analysis of attack intensity

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Steps

  1. 1Install skill using provided installation command
  2. 2Test with simple use case relevant to your work
  3. 3Evaluate output quality and relevance
  4. 4Iterate on prompts to improve results
  5. 5Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use when

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid when

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Related Skills

Reviews

4.862 reviews
  • A
    Amina BrownDec 28, 2024

    detecting-rdp-brute-force-attacks fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • G
    Ganesh MohaneDec 12, 2024

    detecting-rdp-brute-force-attacks reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • W
    William PerezDec 12, 2024

    I recommend detecting-rdp-brute-force-attacks for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • A
    Amina ThompsonNov 19, 2024

    detecting-rdp-brute-force-attacks is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • R
    Rahul SantraNov 3, 2024

    I recommend detecting-rdp-brute-force-attacks for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • X
    Xiao ParkNov 3, 2024

    Solid pick for teams standardizing on skills: detecting-rdp-brute-force-attacks is focused, and the summary matches what you get after install.

  • A
    Advait MalhotraNov 3, 2024

    detecting-rdp-brute-force-attacks reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • P
    Pratham WareOct 22, 2024

    Useful defaults in detecting-rdp-brute-force-attacks — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • K
    Kaira KapoorOct 22, 2024

    detecting-rdp-brute-force-attacks has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • H
    Hiroshi MensahOct 22, 2024

    Registry listing for detecting-rdp-brute-force-attacks matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 62

1 / 7

Discussion

Comments — not star reviews
  • No comments yet — start the thread.