ABUSE.MOM
THREAT REPORT

IP Threat Report
186.53.26.179

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 03:17:25
First seen: 2026-10-08 14:48:44
Last seen: 2026-10-11 01:00:49
95

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
186.53.26.179
Type
Residential
Country
🇺🇾 UY
City
Montevideo
ISP
Administracion Nacional de Telecomunicaciones
Organization
Administracion Nacional de Telecomunicaciones
Autonomous System
AS6057 Administracion Nacional de Telecomunicaciones
Hit Count
50
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 95
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-10-08 14:48:44
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger strong hits: 2 (+50), Foreign referer (+10)
2026-10-11 01:00:49
Last malicious request observed
Total score reached: 95/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Administracion Nacional de Telecomunicaciones
AS6057 · 🇺🇾 UY

We have detected 36 malicious IPs from this autonomous system.

View all IPs from AS6057 →
06

Recommendations

Actions taken & recommended

  • IP 186.53.26.179 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 186.53.26.179 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.

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

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

10

Threat Analysis

186.53.26.179 has been assigned a threat score of 95/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

IP address 186.53.26.179 has been traced to Montevideo, UY, operating on the network of Administracion Nacional de Telecomunicaciones. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 2-day observation window, we recorded 50 hostile requests from this IP — roughly 25 per day on average. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 41 flagged addresses, UY represents a notable presence in our threat database. At 95/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 UY

179.29.108.82 (103)167.58.115.228 (103)167.58.89.217 (103)152.156.190.61 (95)190.134.18.132 (95)View all →

🏢 Same network: AS6057

179.29.108.82 (103)167.58.115.228 (103)167.58.89.217 (103)190.134.18.132 (95)186.49.243.238 (95)View all →
12

Security Intelligence

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 GeoIP Blocking Considerations

Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.

🔍 Check Any IP Address

Share this report: