ABUSE.MOM
THREAT REPORT

IP Threat Report
34.80.18.145

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 23:50:41
First seen: 2026-06-29 03:01:36
Last seen: 2026-07-05 03:57:12
195

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
34.80.18.145
Type
Hosting
Country
🇹🇼 Taiwan
City
Taipei
ISP
Google LLC
Organization
Google Cloud (asia-east1)
Autonomous System
AS396982 Google LLC
Hit Count
193
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 30/10sAbnormally fast request rate — automated scanning+35
Burst 30/2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 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-06-29 03:01:36
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 30/10s (+35), Burst 30/2s (+35), Danger strong hits: 30 (+100)
2026-07-05 03:57:12
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 · 🇹🇼 Taiwan
06

Recommendations

Actions taken & recommended

  • IP 34.80.18.145 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.80.18.145.

🤖 Bot Detection

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

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

34.80.18.145 has been assigned a threat score of 195/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

The address 34.80.18.145 originates from Taipei, Taiwan, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 193 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~32.2 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. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 12 malicious IPs originating from Taiwan, positioning it as a notable contributor to global threat activity. At 195/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 Taiwan

34.81.125.215 (298)35.201.233.251 (288)35.229.166.149 (195)34.81.169.179 (195)35.201.195.226 (195)View all →

🏢 Same network: AS396982

136.67.84.210 (340)34.74.191.44 (340)136.67.103.22 (340)136.66.254.33 (313)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.

💡 Ransomware-as-a-Service Economy

The RaaS model allows technically unskilled criminals to deploy sophisticated ransomware through affiliate programs. Operators provide the malware, infrastructure, and negotiation services, taking a percentage of ransom payments from their affiliates.

🔍 Check Any IP Address

Share this report: