ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.196.132

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 16:28:04
First seen: 2026-08-04 14:58:18
Last seen: 2026-08-09 04:11:09
220

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
173.239.196.132
Type
Hosting
Country
🇲🇲 MM
City
Yangon
ISP
F.N.S. HOLDINGS LIMITED
Organization
LogicWeb Inc
Autonomous System
AS206092 F.N.S. HOLDINGS LIMITED
Hit Count
275
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 7/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 6Medium-risk: admin panels, config files+60
Danger medium hits: 9Medium-risk: admin panels, config files+60
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 330
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-04 14:58:18
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 7/2s (+35), Danger medium hits: 6 (+60), Danger medium hits: 9 (+60)
2026-08-09 04:11:09
Last malicious request observed
Total score reached: 220/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

F.N.S. HOLDINGS LIMITED
AS206092 · 🇲🇲 MM
06

Recommendations

Actions taken & recommended

  • IP 173.239.196.132 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.196.0/24
  • 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 173.239.196.132.

🤖 Bot Detection

Address UA spoofing from 173.239.196.132: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 173.239.196.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
b.barracudacentral.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ 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.196.132 has been assigned a threat score of 220/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:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

The address 173.239.196.132 originates from Yangon, MM, operating on the network of F.N.S. HOLDINGS LIMITED. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 4 days, this IP generated 275 malicious requests, averaging approximately 68.8 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. MM currently accounts for 42 blocked IPs in our database, making it a notable source of malicious traffic. A score of 220/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇲🇲 Top threats from MM

173.239.196.138 (255)173.239.196.139 (255)173.239.196.140 (255)173.239.196.137 (255)173.239.196.142 (255)View all →

🏢 Same network: AS206092

173.239.196.135 (255)173.239.196.129 (255)173.239.196.131 (255)173.239.196.130 (255)173.239.196.134 (255)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.

💡 Edge Computing Attack Surface

Edge computing pushes processing closer to users but expands the attack surface. Edge nodes often run in less secure environments than centralized data centers, creating new opportunities for physical access attacks and supply chain compromises.

🔍 Check Any IP Address

Share this report: