
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 99 | 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: 332 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 880 | Medium-risk: admin panels, config files | +60 | |
| Burst: 40 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 79 | Medium-risk: admin panels, config files | +60 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 37 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger strong hits: 196 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 517 | Medium-risk: admin panels, config files | +60 | |
| Burst: 36 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 166 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 442 | Medium-risk: admin panels, config files | +60 | |
| Burst: 38 req / 10s | Abnormally fast request rate — automated scanning | +35 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Address UA spoofing from 173.239.196.137: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 173.239.196.137.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.
173.239.196.137 has been assigned a threat score of 255/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
Threat intelligence analysis has linked 173.239.196.137 to malicious activity originating from Yangon, MM, operating on the network of F.N.S. HOLDINGS LIMITED. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 9 malicious requests, averaging approximately 9 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. 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. With a threat score of 255/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
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.
Content Security Policy headers instruct browsers to restrict resource loading, mitigating XSS and data injection attacks. Properly configured CSP policies prevent inline script execution, restrict iframe embedding, and control which domains can serve content.