ABUSE.MOM
THREAT REPORT

IP Threat Report
34.175.74.1

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 08:15:00
First seen: 2026-10-25 09:17:56
Last seen: 2026-10-26 08:01:19
238

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
34.175.74.1
Type
Hosting
Country
🇪🇸 Spain
City
Madrid
ISP
Google LLC
Organization
Google Cloud (europe-southwest1)
Autonomous System
AS396982 Google LLC
Hit Count
43
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 25/2sAbnormally fast request rate — automated scanning+35
Burst 83/10sAbnormally 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
Σ = 238
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-10-25 09:17:56
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 25/2s (+35), Burst 83/10s (+35), Danger medium hits: 40 (+60)
2026-10-26 08:01:19
Last malicious request observed
Total score reached: 238/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇪🇸 Spain

We have detected 15127 malicious IPs from this autonomous system.

View all IPs from AS396982 →
06

Recommendations

Actions taken & recommended

  • IP 34.175.74.1 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 34.175.74.0/24
  • 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 34.175.74.1.

07

Neighbors in 34.175.74.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
psbl.surriel.com
✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

34.175.74.1 has been assigned a threat score of 238/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Network traffic from 34.175.74.1, located in Madrid, Spain, operating on the network of Google LLC, has been classified as malicious by our automated threat scoring engine. Our sensors captured 43 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~43 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 811 malicious IPs originating from Spain, positioning it as a major contributor to global threat activity. A score of 238/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 Spain

217.160.136.123 (310)45.67.99.32 (305)212.30.33.72 (305)212.30.33.225 (305)45.67.99.6 (305)View all →

🏢 Same network: AS396982

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

💡 Automated Incident Response

Automated response systems can block threats in milliseconds, far faster than human analysts. However, automation requires careful safeguards — rate limits on blocking actions, automatic expiration, and human review queues prevent automated systems from causing self-inflicted outages.

🔍 Check Any IP Address

Share this report: