Join our Newsletter — 33% off our NHI Course

Why did 21 IPs come to dominate RDP scanning?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: A small hosted fleet generated 49.7% of global RDP Crawler activity over 48 hours and 67.4% on April 7, according to GreyNoise. RDP exposure needs source concentration and burst patterns treated as attack signals, not just scan volume.

Editorial analysis by NHI Mgmt Group, based on content published by GreyNoise: “Just 21 IP Addresses Are Now Behind Nearly Half of All RDP Scanning on the Internet”.

By the numbers:

  • RDP Crawler sessions from AS213438 fell from 1,856,167 on April 7 to 1,795 on April 8 and then to zero on April 9.

Key questions

Q: Why does concentrated RDP scanning increase account compromise risk?

A: Because scanning is the first step in an authentication attack path.

Q: Where does RDP exposure fail in practice?

A: It fails when organisations treat reachability as harmless and leave remote desktop open without strong authentication, monitoring, and restrictions on who can connect.

Q: What should teams do first when exposed RDP starts drawing heavy scan traffic?

A: First, confirm whether the service truly needs internet exposure and remove direct inbound access where possible.

Practitioner guidance

  • Block the four concentrated /24 source blocks Add the Amsterdam and Lelystad network blocks tied to the fleet to inbound RDP scanning block rules and monitor for new source IPs in the same ASN.
  • Review authentication logs on exposed RDP services Look for failed logon bursts, repeated username patterns, and short interval retries from the observed source networks since April 5.
  • Audit non-standard RDP ports at the edge Check for services listening on 3390, 3391, and 3392 as well as standard 3389, because the fleet actively probes alternate ports.

Bottom line: A tiny set of hosted IPs can dominate global RDP probing, which makes source concentration a meaningful security signal rather than a noisy anomaly.

Glossary terms: RDP Scanning, Remote Desktop Protocol, Burst-and-crash infrastructure, Source concentration

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Concentrated scanning changes the defensive problem from volume to source governance. When 21 IPs can account for nearly half of a global probing category, reputation and geolocation baselines lose predictive value very quickly. Teams that still tune controls to country-level patterns will miss how fast hosted infrastructure can rotate or vanish. The practitioner lesson is to govern source concentration as a live risk signal, not a background statistic.

A question worth separating out:

Q: What happens when internet-facing RDP is not tightly governed?

A: A small number of scanners can repeatedly find the service, probe credentials, and create a foothold that looks like a legitimate remote session. That increases the chance of internal access, especially where privileged accounts are reachable from the same endpoint. The governance gap is allowing a high-risk access path to remain broadly available without fast revocation and strong policy enforcement.

👉 Read our full editorial: 21 IPs drive half of global RDP scanning traffic


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.