
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| UA bot: python | Known bot/crawler User-Agent detected | +40 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 31.94.20.253 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Address UA spoofing from 31.94.20.253: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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.
31.94.20.253 has been assigned a threat score of 65/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.
The following attack categories were identified:
Our monitoring infrastructure has identified 31.94.20.253, geolocated to Kirkwall, United Kingdom, operating on the network of British Telecommunications PLC, as a source of suspicious network activity. During its 6-day observation window, we recorded 682 hostile requests from this IP — roughly 113.7 per day on average. 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 Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 139 malicious IPs originating from United Kingdom, positioning it as a significant contributor to global threat activity. The score of 65/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
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.
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.