ABUSE.MOM
THREAT REPORT

IP Threat Report
185.92.25.74

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:54:27
First seen: 2026-05-31 05:55:01
Last seen: 2026-07-12 00:27:29
280

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 280/100. Total malicious requests observed: 18.

BOT_UADANGER_PATH
01

Geolocation & Classification

IP Address
185.92.25.74
Type
Unknown
Country
🇬🇧 United Kingdom
City
Slough
ISP
F.N.S. HOLDINGS LIMITED
Organization
F.N.S. HOLDINGS LIMITED
Autonomous System
Unknown
Hit Count
18
02

Detection Signatures

SignatureDescriptionPointsSeverity
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Danger medium hits: 1Medium-risk: admin panels, config files+10
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Σ = 50
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-05-31 05:55:01
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
DDoS / Flood, Danger medium hits: 1 (+10), UA bot: Go-http-client (+40)
2026-07-12 00:27:29
Last malicious request observed
Total score reached: 280/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 185.92.25.74 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
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 User-Agent Anomaly Defense

IP 185.92.25.74 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

07

Neighbors in 185.92.25.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

185.92.25.74 has been assigned a threat score of 280/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

Network traffic from 185.92.25.74, located in Slough, United Kingdom, operating on the network of F.N.S. HOLDINGS LIMITED, has been classified as malicious by our automated threat scoring engine. Our sensors captured 18 malicious requests from this address across a 41-day span, reflecting a sustained attack cadence of ~0.4 requests per day. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. Our records show 101 malicious IPs originating from United Kingdom, positioning it as a significant contributor to global threat activity. At 280/100, this is an extremely high-risk address. All traffic should be considered hostile.

11

Related Threats

🇬🇧 Top threats from United Kingdom

104.28.240.60 (340)104.28.208.60 (340)91.230.225.239 (305)91.230.225.147 (305)185.92.25.78 (305)View all →
12

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.

💡 Security Header Best Practices

HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.

🔍 Check Any IP Address

Share this report: