ABUSE.MOM
THREAT REPORT

IP Threat Report
176.29.249.183

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 08:00:08
First seen: 2026-05-09 02:00:06
Last seen: 2026-05-09 02:00:06
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
176.29.249.183
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: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 103
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-05-09 02:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), POST requests present (+8)
2026-05-09 02:00:06
Last malicious request observed
Total score reached: 103/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.249.183 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

⚙️ General Security

Add 176.29.249.183 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

176.29.249.183 has been assigned a threat score of 103/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

📊 Threat Analysis

Our monitoring infrastructure has identified 176.29.249.183, geolocated to Amman, JO, operating on the network of ZAIN, as a source of suspicious network activity. 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. JO currently accounts for 78 blocked IPs in our database, making it a notable source of malicious traffic. With a threat score of 103/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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.28.155.119 (83)176.28.168.249 (83)176.28.133.231 (75)View all →
12

Security Intelligence

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: