ABUSE.MOM
THREAT REPORT

IP Threat Report
185.220.101.20

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 09:02:10
First seen: 2026-05-20 13:13:58
Last seen: 2026-05-27 08:52:54
73

⛔ Verdict: BLOCK

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

BOT_UAMETHODRATIO_404REFERER
01

Geolocation & Classification

IP Address
185.220.101.20
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
253
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Σ = 73
03

Observed Activity

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

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

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

04

Timeline

2026-05-20 13:13:58
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Foreign referer (+10), POST seen (+8)
2026-05-27 08:52:54
Last malicious request observed
Total score reached: 73/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 185.220.101.20 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 185.220.101.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

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

🤖 Bot Detection

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

07

Neighbors in 185.220.101.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de

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

10

Threat Analysis

185.220.101.20 has been assigned a threat score of 73/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

185.220.101.20 is registered in an unknown location. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 6-day observation window, we recorded 253 hostile requests from this IP — roughly 42.2 per day on average. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. A threat score of 73/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.

11

Related Threats

🇤🇤 Top threats from ??

View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Command Injection Techniques

Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.

🔍 Check Any IP Address

Share this report: