ABUSE.MOM
THREAT REPORT

IP Threat Report
34.165.223.19

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 20:35:16
First seen: 2026-05-15 14:00:06
Last seen: 2026-05-15 14:00:06
195

⛔ Verdict: BLOCK

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

UA_CHANGEDDANGER_PATHBURST
01

Geolocation & Classification

IP Address
34.165.223.19
Type
Hosting
Country
🇮🇱 IL
City
Tel Aviv
ISP
Google LLC
Organization
Google Cloud (me-west1)
Autonomous System
AS396982 Google LLC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Burst: 10 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 10 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 195
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-05-15 14:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger strong hits: 10 (+100), Burst: 10 req / 2s (+35)
2026-05-15 14:00:06
Last malicious request observed
Total score reached: 195/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇮🇱 IL
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

Address UA spoofing from 34.165.223.19: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

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

✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

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

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

IP address 34.165.223.19 has been traced to Tel Aviv, IL, operating on the network of Google LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 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. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 101 flagged addresses, IL represents a significant presence in our threat database. With a threat score of 195/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 IL

203.159.81.66 (255)203.159.81.57 (255)203.159.81.77 (255)203.159.81.93 (255)203.159.81.81 (255)View all →

🏢 Same network: AS396982

34.165.140.201 (220)34.165.133.118 (195)34.165.154.193 (195)34.165.206.38 (195)34.165.16.107 (145)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Zero-Day Vulnerability Markets

Zero-day vulnerabilities command premium prices in both legitimate and criminal markets. Government agencies, defensive security firms, and criminal organizations compete for these undisclosed flaws, creating a complex ecosystem around vulnerability discovery and disclosure.

🔍 Check Any IP Address

Share this report: