
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: 338 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 742 | Medium-risk: admin panels, config files | +60 | |
| Burst: 36 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 120 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
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 185.192.71.118: 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 185.192.71.118.
Block scanning from 185.192.71.118: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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.
185.192.71.118 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:
Our monitoring infrastructure has identified 185.192.71.118, geolocated to London, United Kingdom, operating on the network of F.N.S. HOLDINGS LIMITED, as a source of suspicious network activity. The address has been active for 26 days in our monitoring system, producing 2 flagged requests at a rate of ~0.1/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 150 malicious IPs originating from United Kingdom, positioning it as a significant 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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
Analyzing attack patterns at the AS (Autonomous System) level reveals which networks harbor the most malicious activity. Some ASes have abuse rates orders of magnitude higher than average, indicating lax enforcement of acceptable use policies.