ABUSE.MOM
THREAT REPORT

IP Threat Report
176.18.31.11

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 17:49:29
First seen: 2026-07-30 04:30:21
Last seen: 2026-08-02 00:50:17
60

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
176.18.31.11
Type
Mobile
Country
🇸🇦 SA
City
Jeddah
ISP
Internet Broadband
Organization
Unknown
Autonomous System
AS35819 Etihad Etisalat, a joint stock company
Hit Count
159
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-07-30 04:30:21
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-02 00:50:17
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 176.18.31.11 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 176.18.31.11 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
cbl.abuseat.org
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

Network traffic from 176.18.31.11, located in Jeddah, SA, operating on the network of Internet Broadband, has been classified as malicious by our automated threat scoring engine. During its 2-day observation window, we recorded 159 hostile requests from this IP — roughly 79.5 per day on average. 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. Our records show 106 malicious IPs originating from SA, positioning it as a significant contributor to global threat activity. 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)178.73.74.53 (60)5.111.204.29 (60)View all →
12

Security Intelligence

💡 Remote Code Execution (RCE)

RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.

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

🔍 Check Any IP Address

Share this report: