
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 173.239.211.33 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 173.239.211.33 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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.211.33 has been assigned a threat score of 65/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
Our monitoring infrastructure has identified 173.239.211.33, geolocated to an unknown location, as a source of suspicious network activity. Over a period of 1 days, this IP generated 106 malicious requests, averaging approximately 106 requests per day. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.
Mobile carrier NAT (CGNAT) means thousands of users share a single public IP, making mobile IPs unreliable for reputation scoring. However, mobile networks are increasingly used as attack platforms through compromised apps and malicious SDKs.