ABUSE.MOM
THREAT REPORT

IP Threat Report
35.194.114.122

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-06 01:45:17
First seen: 2026-08-30 13:23:27
Last seen: 2026-09-06 01:04:29
263

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODUA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 121/10sAbnormally fast request rate — automated scanning+35
Burst 54/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
Σ = 263
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:27
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 121/10s (+35), Burst 54/2s (+35), Danger medium hits: 15 (+60)
2026-09-06 01:04:29
Last malicious request observed
Total score reached: 263/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 35.194.114.122 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

🌊 Traffic Flood Defense

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

🤖 Bot Detection

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

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

10

Threat Analysis

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

📊 Threat Analysis

35.194.114.122 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. Over a period of 6 days, this IP generated 192 malicious requests, averaging approximately 32 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Japan currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 263/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 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

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.

💡 Autonomous System Analysis

Analyzing attack patterns at the AS (Autonomous System) level reveals which networks harbor the most malicious activity. Some ASes have abuse rates orders of magnitude higher than average, indicating lax enforcement of acceptable use policies.

🔍 Check Any IP Address

Share this report: