ABUSE.MOM
THREAT REPORT

IP Threat Report
207.175.112.175

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-24 19:58:16
First seen: 2026-09-20 18:57:47
Last seen: 2026-09-27 01:37:25
263

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODUA_CHANGED
01

Geolocation & Classification

IP Address
207.175.112.175
Type
Hosting
Country
🇧🇪 Belgium
City
Brussels
ISP
Google LLC
Organization
Google Cloud (europe-west1)
Autonomous System
AS396982 Google LLC
Hit Count
166
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 65/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 40Medium-risk: admin panels, config files+60
Danger strong hits: 241High-risk paths: shells, RCE vectors, exploits+100
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 263
03

Observed Activity

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

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

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

04

Timeline

2026-09-20 18:57:47
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 200/10s (+35), Burst 65/2s (+35), Danger medium hits: 40 (+60)
2026-09-27 01:37:25
Last malicious request observed
Total score reached: 263/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇧🇪 Belgium

We have detected 8214 malicious IPs from this autonomous system.

View all IPs from AS396982 →
06

Recommendations

Actions taken & recommended

  • IP 207.175.112.175 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 207.175.112.175.

🤖 User-Agent Anomaly Defense

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

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

207.175.112.175 has been assigned a threat score of 263/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:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 207.175.112.175 has been traced to Brussels, Belgium, operating on the network of Google LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 166 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~27.7 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 839 malicious IPs originating from Belgium, positioning it as a major contributor to global threat activity. A score of 263/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇧🇪 Top threats from Belgium

34.78.110.28 (348)34.52.216.81 (313)34.38.157.42 (313)34.78.158.246 (313)34.156.192.235 (313)View all →

🏢 Same network: AS396982

34.78.110.28 (348)136.67.84.210 (340)34.74.191.44 (340)136.67.103.22 (340)35.254.195.37 (340)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.

💡 Data Center IP Reputation

IPs originating from data centers and hosting providers account for a disproportionate amount of malicious traffic. Compromised VPS instances, bulletproof hosting, and abused trial accounts create persistent attack infrastructure that can be difficult to shut down.

🔍 Check Any IP Address

Share this report: