ABUSE.MOM
THREAT REPORT

IP Threat Report
35.189.147.64

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-24 19:20:09
First seen: 2026-09-16 03:43:13
Last seen: 2026-09-20 02:13:17
268

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODREDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
35.189.147.64
Type
Hosting
Country
🇯🇵 Japan
City
Tokyo
ISP
Google LLC
Organization
Google Cloud (asia-northeast1)
Autonomous System
AS396982 Google LLC
Hit Count
110
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 11/2sAbnormally fast request rate — automated scanning+35
Burst 33/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 30Medium-risk: admin panels, config files+60
Danger strong hits: 52High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 268
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-16 03:43:13
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 11/2s (+35), Burst 33/10s (+35), Danger medium hits: 30 (+60)
2026-09-20 02:13:17
Last malicious request observed
Total score reached: 268/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇯🇵 Japan

We have detected 8216 malicious IPs from this autonomous system.

View all IPs from AS396982 →
06

Recommendations

Actions taken & recommended

  • IP 35.189.147.64 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 35.189.147.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Traffic Flood Defense

IP 35.189.147.64 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🔎 Path Enumeration Protection

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

07

Neighbors in 35.189.147.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

35.189.147.64 has been assigned a threat score of 268/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 FloodingPath Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 35.189.147.64, geolocated to Tokyo, Japan, operating on the network of Google LLC, as a source of suspicious network activity. Our sensors captured 110 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~36.7 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 Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Japan currently accounts for 1,341 blocked IPs in our database, making it a major source of malicious traffic. A score of 268/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)168.110.58.114 (320)129.225.172.187 (310)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)35.254.195.37 (340)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.

💡 Security Header Best Practices

HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.

🔍 Check Any IP Address

Share this report: