ABUSE.MOM
THREAT REPORT

IP Threat Report
35.252.17.101

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-11-01 01:43:07
First seen: 2026-10-31 04:14:29
Last seen: 2026-11-01 01:25:54
263

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODUA_CHANGED
01

Geolocation & Classification

IP Address
35.252.17.101
Type
Hosting
Country
🇮🇱 IL
City
Tel Aviv
ISP
Google LLC
Organization
Google Cloud (me-west1)
Autonomous System
AS396982 Google LLC
Hit Count
545
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 101/10sAbnormally fast request rate — automated scanning+35
Burst 102/10sAbnormally fast request rate — automated scanning+35
Burst 103/10sAbnormally fast request rate — automated scanning+35
Burst 104/10sAbnormally fast request rate — automated scanning+35
Burst 105/10sAbnormally fast request rate — automated scanning+35
Burst 108/10sAbnormally fast request rate — automated scanning+35
Burst 109/10sAbnormally fast request rate — automated scanning+35
Burst 111/10sAbnormally fast request rate — automated scanning+35
Burst 20/2sAbnormally fast request rate — automated scanning+35
Burst 21/2sAbnormally fast request rate — automated scanning+35
Burst 23/2sAbnormally fast request rate — automated scanning+35
Burst 24/2sAbnormally fast request rate — automated scanning+35
Burst 26/2sAbnormally fast request rate — automated scanning+35
Burst 27/2sAbnormally fast request rate — automated scanning+35
Burst 28/2sAbnormally fast request rate — automated scanning+35
Burst 29/2sAbnormally fast request rate — automated scanning+35
Burst 30/2sAbnormally fast request rate — automated scanning+35
Burst 31/2sAbnormally fast request rate — automated scanning+35
Burst 63/10sAbnormally fast request rate — automated scanning+35
Burst 68/10sAbnormally fast request rate — automated scanning+35
Burst 73/10sAbnormally fast request rate — automated scanning+35
Burst 74/10sAbnormally fast request rate — automated scanning+35
Burst 80/10sAbnormally fast request rate — automated scanning+35
Burst 90/10sAbnormally fast request rate — automated scanning+35
Burst 91/10sAbnormally fast request rate — automated scanning+35
Burst 92/10sAbnormally fast request rate — automated scanning+35
Burst 93/10sAbnormally fast request rate — automated scanning+35
Burst 94/10sAbnormally fast request rate — automated scanning+35
Burst 99/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 38Medium-risk: admin panels, config files+60
Danger medium hits: 40Medium-risk: admin panels, config files+60
Danger strong hits: 159High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 239High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 241High-risk paths: shells, RCE vectors, exploits+100
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 1468
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-10-31 04:14:29
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 101/10s (+35), Burst 102/10s (+35), Burst 103/10s (+35)
2026-11-01 01:25:54
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 · 🇮🇱 IL

We have detected 15228 malicious IPs from this autonomous system.

View all IPs from AS396982 →
06

Recommendations

Actions taken & recommended

  • IP 35.252.17.101 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 35.252.17.101.

🤖 User-Agent Anomaly Defense

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

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

10

Threat Analysis

35.252.17.101 has been assigned a threat score of 263/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

Threat intelligence analysis has linked 35.252.17.101 to malicious activity originating from Tel Aviv, IL, operating on the network of Google LLC. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 545 malicious requests, averaging approximately 545 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 User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. IL currently accounts for 212 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 IL

203.159.81.84 (305)203.159.81.33 (305)203.159.81.99 (295)34.165.185.29 (288)35.252.29.160 (288)View all →

🏢 Same network: AS396982

34.78.110.28 (348)34.187.158.4 (340)34.186.187.208 (340)136.67.84.210 (340)34.74.191.44 (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.

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

🔍 Check Any IP Address

Share this report: