ABUSE.MOM
THREAT REPORT

IP Threat Report
34.97.88.203

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 10:39:10
First seen: 2026-08-30 13:23:25
Last seen: 2026-09-06 01:04:12
288

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODRATIO_404UA_CHANGED
01

Geolocation & Classification

IP Address
34.97.88.203
Type
Hosting
Country
🇯🇵 Japan
City
Osaka
ISP
Google LLC
Organization
Google Cloud (asia-northeast2)
Autonomous System
AS396982 Google LLC
Hit Count
139
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 149/10sAbnormally fast request rate — automated scanning+35
Burst 74/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 15Medium-risk: admin panels, config files+60
Danger strong hits: 44High-risk paths: shells, RCE vectors, exploits+100
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 288
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-08-30 13:23:25
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 149/10s (+35), Burst 74/2s (+35)
2026-09-06 01:04:12
Last malicious request observed
Total score reached: 288/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

Block scanning from 34.97.88.203: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

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

🤖 User-Agent Anomaly Defense

IP 34.97.88.203 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

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

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

10

Threat Analysis

34.97.88.203 has been assigned a threat score of 288/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

The address 34.97.88.203 originates from Osaka, Japan, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 139 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~23.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. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. With 104 flagged addresses, Japan represents a significant presence in our threat database. A score of 288/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 Japan

103.163.220.216 (340)35.189.151.182 (320)168.110.63.243 (320)129.225.172.187 (310)194.5.48.175 (305)View all →

🏢 Same network: AS396982

136.110.108.43 (303)35.221.86.161 (298)34.104.189.15 (298)35.200.81.158 (298)34.146.116.8 (298)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.

💡 IP Geolocation Accuracy Limitations

IP geolocation databases provide approximate locations with varying accuracy. City-level geolocation is typically 50-80% accurate, while country-level exceeds 95%. VPNs, proxies, and mobile networks further reduce reliability, making geolocation a useful but imperfect intelligence signal.

🔍 Check Any IP Address

Share this report: