ABUSE.MOM
THREAT REPORT

IP Threat Report
34.80.5.240

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 02:37:58
First seen: 2026-09-07 17:56:35
Last seen: 2026-09-13 01:14:52
238

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHOD
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 13/2sAbnormally fast request rate — automated scanning+35
Burst 46/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-07 17:56:35
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 13/2s (+35), Burst 46/10s (+35), Danger medium hits: 40 (+60)
2026-09-13 01:14:52
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 · 🇹🇼 Taiwan
06

Recommendations

Actions taken & recommended

  • IP 34.80.5.240 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.5.240.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

34.80.5.240 has been assigned a threat score of 238/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 34.80.5.240, geolocated to Taipei, Taiwan, operating on the network of Google LLC, as a source of suspicious network activity. Over a period of 5 days, this IP generated 145 malicious requests, averaging approximately 29 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Taiwan currently accounts for 101 blocked IPs in our database, making it a significant 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 Taiwan

34.81.125.215 (298)35.201.157.167 (298)104.199.142.243 (298)35.229.133.140 (298)35.194.199.14 (298)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.

💡 Passive DNS for Threat Hunting

Passive DNS databases record historical DNS resolution data, enabling analysts to track domain changes, identify related infrastructure, and discover malicious domains sharing hosting with known threats. This historical context is invaluable for threat investigation.

🔍 Check Any IP Address

Share this report: