ABUSE.MOM
THREAT REPORT

IP Threat Report
176.29.123.195

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 08:00:08
First seen: 2026-04-06 21:00:06
Last seen: 2026-04-06 21:00:06
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
176.29.123.195
Type
Mobile
Country
🇯🇴 JO
City
Amman
ISP
ZAIN
Organization
Unknown
Autonomous System
AS48832 Jordanian mobile phone services Ltd
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-04-06 21:00:06
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-04-06 21:00:06
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

ZAIN
AS48832 · 🇯🇴 JO
06

Recommendations

Actions taken & recommended

  • IP 176.29.123.195 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.29.123.195 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
zen.spamhaus.org
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

176.29.123.195 has been assigned a threat score of 68/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

The address 176.29.123.195 originates from Amman, JO, operating on the network of ZAIN. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. JO currently accounts for 78 blocked IPs in our database, making it a notable source of malicious traffic. The score of 68/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

11

Related Threats

🇯🇴 Top threats from JO

91.186.252.91 (208)176.29.225.112 (198)91.186.255.110 (168)109.107.243.93 (128)176.28.170.254 (128)View all →

🏢 Same network: AS48832

176.29.225.112 (198)176.28.170.254 (128)176.29.249.183 (103)176.28.155.119 (83)176.28.168.249 (83)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 Behavioral Analysis vs Signature Detection

Signature-based detection matches known attack patterns but misses novel threats. Behavioral analysis identifies anomalies in request patterns, timing, and volume, catching zero-day attacks that signatures cannot recognize.

🔍 Check Any IP Address

Share this report: