ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.236.80

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:21:27
First seen: 2026-05-05 12:00:04
Last seen: 2026-05-05 12:00:04
305

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHRATIO_404BURSTREFERER
01

Geolocation & Classification

IP Address
173.239.236.80
Type
Residential
Country
🇲🇾 MY
City
Kuala Lumpur
ISP
LogicWeb Inc.
Organization
Epik Holdings Inc
Autonomous System
AS206092 F.N.S. HOLDINGS LIMITED
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Danger strong hits: 456High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 358Medium-risk: admin panels, config files+60
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 8 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 305
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-05-05 12:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: Go-http-client (+40), Danger strong hits: 456 (+100), Danger medium hits: 358 (+60)
2026-05-05 12:00:04
Last malicious request observed
Total score reached: 305/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

LogicWeb Inc.
AS206092 · 🇲🇾 MY
06

Recommendations

Actions taken & recommended

  • IP 173.239.236.80 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 173.239.236.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 User-Agent Anomaly Defense

IP 173.239.236.80 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🔎 Directory Scan Defense

IP 173.239.236.80 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Flood / DDoS Mitigation

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

07

Neighbors in 173.239.236.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

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

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

10

Threat Analysis

173.239.236.80 has been assigned a threat score of 305/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

IP address 173.239.236.80 has been traced to Kuala Lumpur, MY, operating on the network of LogicWeb Inc.. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. At 305/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 MY

173.239.236.211 (255)View all →

🏢 Same network: AS206092

103.163.220.216 (340)85.203.21.101 (320)85.203.21.157 (310)85.203.21.172 (305)91.217.249.222 (305)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 Backup and Recovery Against Ransomware

Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.

🔍 Check Any IP Address

Share this report: