ABUSE.MOM
THREAT REPORT

IP Threat Report
34.84.4.148

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 23:50:41
First seen: 2026-06-29 03:37:38
Last seen: 2026-07-05 03:49:25
195

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
34.84.4.148
Type
Hosting
Country
🇯🇵 Japan
City
Tokyo
ISP
Google LLC
Organization
Google Cloud (asia-northeast1)
Autonomous System
AS396982 Google LLC
Hit Count
145
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:37:38
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:49:25
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 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

  • IP 34.84.4.148 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.84.4.148.

🤖 Bot Detection

Address UA spoofing from 34.84.4.148: 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
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
cbl.abuseat.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de

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

10

Threat Analysis

34.84.4.148 has been assigned a threat score of 195/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 FloodingUser-Agent Anomaly

📊 Threat Analysis

34.84.4.148 is registered in Tokyo, Japan, operating on the network of Google LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 6 days in our monitoring system, producing 145 flagged requests at a rate of ~24.2/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. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 106 malicious IPs originating from Japan, positioning it as a significant contributor to global threat activity. 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 Japan

103.163.220.216 (340)35.189.151.182 (320)194.5.48.175 (305)34.97.45.15 (295)35.243.110.60 (288)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.

💡 DNS-Based Threat Detection

Monitoring DNS queries reveals malicious activity including command-and-control communication, data exfiltration through DNS tunneling, and connections to known malicious domains. DNS is often the first indicator of compromise in network forensics.

🔍 Check Any IP Address

Share this report: