ABUSE.MOM
THREAT REPORT

IP Threat Report
5.162.94.93

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 17:38:53
First seen: 2026-08-05 13:25:18
Last seen: 2026-08-09 04:16:59
70

⛔ Verdict: BLOCK

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

BURST
01

Geolocation & Classification

IP Address
5.162.94.93
Type
Residential
Country
🇴🇲 OM
City
Muscat
ISP
Nawras ISP (Oman)
Organization
Nawras (Oman)
Autonomous System
AS50010 Omani Qatari Telecommunication Company SAOC
Hit Count
119
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 29/10sAbnormally fast request rate — automated scanning+35
Burst 9/2sAbnormally fast request rate — automated scanning+35
Σ = 70
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-08-05 13:25:18
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 29/10s (+35), Burst 9/2s (+35)
2026-08-09 04:16:59
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Nawras ISP (Oman)
AS50010 · 🇴🇲 OM
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 5.162.94.93.

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
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

5.162.94.93 has been assigned a threat score of 70/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:

Request Flooding

📊 Threat Analysis

5.162.94.93 is registered in Muscat, OM, operating on the network of Nawras ISP (Oman). This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 3-day observation window, we recorded 119 hostile requests from this IP — roughly 39.7 per day on average. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. With 102 flagged addresses, OM represents a significant presence in our threat database. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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 OM

5.37.220.174 (180)5.36.230.77 (180)5.37.105.224 (165)5.37.219.191 (165)5.37.148.74 (165)View all →

🏢 Same network: AS50010

5.21.236.143 (70)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Botnet Command and Control Evolution

Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.

🔍 Check Any IP Address

Share this report: