IP Threat Report
185.92.25.102
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 16/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 17/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 32/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 32 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 |
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 185.92.25.102 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 185.92.25.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🌊 Traffic Flood Defense
IP 185.92.25.102 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🤖 Bot Detection
Address UA spoofing from 185.92.25.102: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Neighbors in 185.92.25.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
185.92.25.102 has been assigned a threat score of 270/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
📊 Threat Analysis
IP address 185.92.25.102 has been traced to Slough, United Kingdom, operating on the network of F.N.S. HOLDINGS LIMITED. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 7-day observation window, we recorded 128 hostile requests from this IP — roughly 18.3 per day on average. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 82 malicious IPs originating from United Kingdom, positioning it as a notable contributor to global threat activity. At 270/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.
Related Threats
🇬🇧 Top threats from United Kingdom
91.230.225.166 (320)185.92.25.3 (305)91.230.225.140 (305)91.230.225.6 (305)185.92.25.6 (305)View all →Security Intelligence
💡 DDoS Mitigation Approaches
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
💡 Subdomain Takeover Vulnerabilities
Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.