ABUSE.MOM
THREAT REPORT

IP Threat Report
34.18.221.137

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 22:24:55
First seen: 2026-09-12 06:29:21
Last seen: 2026-09-13 00:03:36
238

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
34.18.221.137
Type
Hosting
Country
🇶🇦 QA
City
Doha
ISP
Google LLC
Organization
Google Cloud (me-central1)
Autonomous System
AS396982 Google LLC
Hit Count
23
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 20/2sAbnormally fast request rate — automated scanning+35
Burst 73/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-09-12 06:29:21
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 20/2s (+35), Burst 73/10s (+35), Danger medium hits: 40 (+60)
2026-09-13 00:03:36
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 · 🇶🇦 QA
06

Recommendations

Actions taken & recommended

  • IP 34.18.221.137 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 34.18.221.137.

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

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

10

Threat Analysis

34.18.221.137 has been assigned a threat score of 238/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

34.18.221.137 is registered in Doha, QA, operating on the network of Google LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 23 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~23 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. QA currently accounts for 76 blocked IPs in our database, making it a notable source of malicious traffic. With a threat score of 238/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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 QA

34.18.122.186 (288)34.18.235.87 (288)34.18.209.41 (288)34.18.110.181 (263)34.18.114.23 (263)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)34.52.216.81 (313)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.

💡 TLS Certificate Misconfigurations

Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.

🔍 Check Any IP Address

Share this report: