ABUSE.MOM
THREAT REPORT

IP Threat Report
4.211.172.220

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 06:11:18
First seen: 2026-02-23 17:00:05
Last seen: 2026-02-24 02:00:07
245

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 245/100. Total malicious requests observed: 13.

UA_SUSDANGER_PATHRATIO_404REDIRECT_PROBEBURST
01

Geolocation & Classification

IP Address
4.211.172.220
Type
Hosting
Country
🇫🇷 France
City
Paris
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (francecentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
13
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 114Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 46 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 15 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 49 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Burst: 51 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 14 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 50 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 101Medium-risk: admin panels, config files+60
Burst: 47 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 111Medium-risk: admin panels, config files+60
Danger medium hits: 166Medium-risk: admin panels, config files+60
Burst: 36 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 113 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 168Medium-risk: admin panels, config files+60
Burst: 44 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 144 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 112Medium-risk: admin panels, config files+60
Burst: 38 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 123 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 1125
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-02-23 17:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 2 (+50), Danger medium hits: 114 (+60)
2026-02-24 02:00:07
Last malicious request observed
Total score reached: 245/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇫🇷 France
06

Recommendations

Actions taken & recommended

  • IP 4.211.172.220 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

Address UA spoofing from 4.211.172.220: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🔎 Directory Scan Defense

IP 4.211.172.220 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 4.211.172.220.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

⛔ LISTED
Spamhaus ZEN

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

4.211.172.220 has been assigned a threat score of 245/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

Network traffic from 4.211.172.220, located in Paris, France, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 13 malicious requests, averaging approximately 13 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. France currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 245/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇫🇷 Top threats from France

185.177.72.11 (348)185.177.72.67 (348)185.177.72.10 (348)185.177.72.16 (348)185.177.72.69 (348)View all →

🏢 Same network: AS8075

74.241.249.229 (340)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)20.29.71.103 (283)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 Botnet Command and Control Evolution

Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.

🔍 Check Any IP Address

Share this report: