ABUSE.MOM
THREAT REPORT

IP Threat Report
185.80.226.52

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 11:09:39
First seen: 2026-03-08 12:00:04
Last seen: 2026-03-08 12:00:04
68

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404METHOD
01

Geolocation & Classification

IP Address
185.80.226.52
Type
Residential
Country
🇦🇱 AL
City
Patos
ISP
IPRO Sh.p.k.
Organization
IPRO Sh.p.k
Autonomous System
AS201249 IPRO Sh.p.k.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 68
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-03-08 12:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 1 (+25), Danger medium hits: 1 (+10), 404 ratio >= 60% (+25)
2026-03-08 12:00:04
Last malicious request observed
Total score reached: 68/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

IPRO Sh.p.k.
AS201249 · 🇦🇱 AL
06

Recommendations

Actions taken & recommended

  • IP 185.80.226.52 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

🔎 Directory Scan Defense

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

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

185.80.226.52 has been assigned a threat score of 68/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

185.80.226.52 is registered in Patos, AL, operating on the network of IPRO Sh.p.k.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 61 flagged addresses, AL represents a notable presence in our threat database. The score of 68/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇦🇱 Top threats from AL

78.159.131.56 (265)217.9.247.118 (255)151.245.116.70 (255)151.245.116.148 (255)217.9.247.11 (255)View all →

🏢 Same network: AS201249

View all →
12

Security Intelligence

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

💡 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.

🔍 Check Any IP Address

Share this report: