IP Threat Report
173.239.196.143
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 240 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 638 | Medium-risk: admin panels, config files | +60 | |
| Burst: 13 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 44 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 66 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 41 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 122 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 321 | Medium-risk: admin panels, config files | +60 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 39 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 33 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 101 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 26 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 74 | Medium-risk: admin panels, config files | +60 | |
| Burst: 37 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 99 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 334 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 882 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 311 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 815 | Medium-risk: admin panels, config files | +60 | |
| Burst: 38 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Burst: 10 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 13 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 51 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 144 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Danger strong hits: 45 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 137 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 108 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 264 | Medium-risk: admin panels, config files | +60 | |
| Burst: 42 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 173.239.196.143 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
🤖 User-Agent Anomaly Defense
IP 173.239.196.143 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🌊 Traffic Flood Defense
IP 173.239.196.143 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Neighbors in 173.239.196.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
173.239.196.143 has been assigned a threat score of 255/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:
📊 Threat Analysis
Our monitoring infrastructure has identified 173.239.196.143, geolocated to Yangon, MM, operating on the network of F.N.S. HOLDINGS LIMITED, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 15 flagged requests at a rate of ~15/day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 31 malicious IPs originating from MM, positioning it as a notable contributor to global threat activity. At 255/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.
Related Threats
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.
💡 Phishing Infrastructure Analysis
Modern phishing operations use sophisticated infrastructure including lookalike domains, valid TLS certificates, and evasion techniques like cloaking and geofencing. Analyzing this infrastructure reveals campaigns before they reach their targets.