ABUSE.MOM
THREAT REPORT

IP Threat Report
34.1.2.180

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 12:46:22
First seen: 2026-03-04 13:00:04
Last seen: 2026-03-04 13:00:04
70

⛔ Verdict: BLOCK

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

BURST
01

Geolocation & Classification

IP Address
34.1.2.180
Type
Hosting
Country
🇫🇷 France
City
Paris
ISP
Google LLC
Organization
Google Cloud (europe-west9)
Autonomous System
AS15169 Google LLC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 11 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 70
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-03-04 13:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 6 req / 2s (+35), Burst: 11 req / 10s (+35)
2026-03-04 13:00:04
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS15169 · 🇫🇷 France
06

Recommendations

Actions taken & recommended

  • IP 34.1.2.180 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

🌊 Traffic Flood Defense

IP 34.1.2.180 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

34.1.2.180 has been assigned a threat score of 70/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 34.1.2.180, geolocated to Paris, France, operating on the network of Google LLC, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/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 IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Our records show 101 malicious IPs originating from France, positioning it as a significant contributor to global threat activity. At 70/100, this IP warrants immediate defensive action.

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 France

185.177.72.67 (348)185.177.72.10 (348)185.177.72.69 (348)185.177.72.29 (348)185.177.72.16 (348)View all →

🏢 Same network: AS15169

66.249.82.32 (205)74.125.217.40 (175)192.178.11.96 (170)35.212.230.168 (170)209.85.238.2 (165)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.

💡 IPv6 Scanning Challenges

The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.

🔍 Check Any IP Address

Share this report: