ABUSE.MOM
THREAT REPORT

IP Threat Report
185.220.101.181

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:21:31
First seen: 2026-05-20 08:01:07
Last seen: 2026-05-27 05:53:33
73

⛔ Verdict: BLOCK

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

BOT_UAMETHODRATIO_404REFERERUA_SUS
01

Geolocation & Classification

IP Address
185.220.101.181
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
153
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
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 88
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 08:01:07
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 05:53:33
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.181 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

🔎 Path Enumeration Protection

Block scanning from 185.220.101.181: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 User-Agent Anomaly Defense

IP 185.220.101.181 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

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
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

185.220.101.181 has been assigned a threat score of 73/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 185.220.101.181, geolocated to an unknown location, as a source of suspicious network activity. The address has been active for 6 days in our monitoring system, producing 153 flagged requests at a rate of ~25.5/day. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. At 73/100, this IP warrants immediate defensive action.

11

Related Threats

🇤🇤 Top threats from ??

View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 Subdomain Takeover Vulnerabilities

Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.

🔍 Check Any IP Address

Share this report: