ABUSE.MOM
THREAT REPORT

IP Threat Report
5.111.204.29

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 17:49:29
First seen: 2026-08-04 11:56:04
Last seen: 2026-08-09 04:08:22
60

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
5.111.204.29
Type
Mobile
Country
🇸🇦 SA
City
Jeddah
ISP
Internet Broadband
Organization
Unknown
Autonomous System
AS35819 Etihad Etisalat, a joint stock company
Hit Count
167
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Foreign refererReferer from unrelated external domain+10
Σ = 60
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-08-04 11:56:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger strong hits: 1 (+25), Foreign referer (+10)
2026-08-09 04:08:22
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Internet Broadband
AS35819 · 🇸🇦 SA
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

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

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

5.111.204.29 has been assigned a threat score of 60/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 Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 5.111.204.29, geolocated to Jeddah, SA, operating on the network of Internet Broadband, as a source of suspicious network activity. Our sensors captured 167 malicious requests from this address across a 4-day span, reflecting a sustained attack cadence of ~41.8 requests per day. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 106 flagged addresses, SA represents a significant presence in our threat database. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

11

Related Threats

🇸🇦 Top threats from SA

81.208.175.87 (320)34.166.187.0 (285)145.241.159.130 (270)8.228.201.198 (263)34.166.126.0 (263)View all →

🏢 Same network: AS35819

31.166.236.247 (120)178.73.81.104 (60)46.52.85.156 (60)176.18.31.11 (60)178.73.74.53 (60)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 Content Security Policy Implementation

Content Security Policy headers instruct browsers to restrict resource loading, mitigating XSS and data injection attacks. Properly configured CSP policies prevent inline script execution, restrict iframe embedding, and control which domains can serve content.

🔍 Check Any IP Address

Share this report: