ABUSE.MOM
THREAT REPORT

IP Threat Report
5.32.247.130

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 10:04:04
First seen: 2026-03-21 01:00:07
Last seen: 2026-03-21 06:00:07
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
5.32.247.130
Type
Mobile
Country
🇴🇲 OM
City
Muscat
ISP
OmanMobile Telecommunication company LLC
Organization
OmanMobile Telecommunication company
Autonomous System
AS28885 OmanTel NAP
Hit Count
2
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-03-21 01:00:07
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-03-21 06:00:07
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

OmanMobile Telecommunication company LLC
AS28885 · 🇴🇲 OM
06

Recommendations

Actions taken & recommended

  • IP 5.32.247.130 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 5.32.247.130 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.

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

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

10

Threat Analysis

5.32.247.130 has been assigned a threat score of 103/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

📊 Threat Analysis

Threat intelligence analysis has linked 5.32.247.130 to malicious activity originating from Muscat, OM, operating on the network of OmanMobile Telecommunication company LLC. The address has been under observation since its initial detection. Our sensors captured 2 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~2 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. OM currently accounts for 107 blocked IPs in our database, making it a significant 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 OM

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

🏢 Same network: AS28885

5.37.220.174 (180)5.36.230.77 (180)5.37.142.107 (165)5.37.219.191 (165)5.37.105.224 (165)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.

💡 Network Flow Analysis

Analyzing network flows (NetFlow, sFlow, IPFIX) provides visibility into traffic patterns without inspecting packet contents. Flow data reveals scanning activity, data exfiltration, lateral movement, and command-and-control channels at scale.

🔍 Check Any IP Address

Share this report: