ABUSE.MOM
THREAT REPORT

IP Threat Report
35.252.29.158

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-24 23:20:10
First seen: 2026-09-17 09:00:21
Last seen: 2026-09-20 02:15:38
238

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHOD
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 113/10sAbnormally fast request rate — automated scanning+35
Burst 31/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 40Medium-risk: admin panels, config files+60
Danger strong hits: 241High-risk paths: shells, RCE vectors, exploits+100
POST seenBehavioral anomaly detected by automated analysis+8
Σ = 238
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-17 09:00:21
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 113/10s (+35), Burst 31/2s (+35), Danger medium hits: 40 (+60)
2026-09-20 02:15:38
Last malicious request observed
Total score reached: 238/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 8217 malicious IPs from this autonomous system.

View all IPs from AS396982 →
06

Recommendations

Actions taken & recommended

  • IP 35.252.29.158 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.252.29.0/24
  • 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.29.158.

07

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

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

10

Threat Analysis

35.252.29.158 has been assigned a threat score of 238/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:

Request Flooding

📊 Threat Analysis

35.252.29.158 is registered in Tel Aviv, IL, 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 2 days in our monitoring system, producing 76 flagged requests at a rate of ~38/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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. IL currently accounts for 205 blocked IPs in our database, making it a significant source of malicious traffic. At 238/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)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.

💡 Automated Incident Response

Automated response systems can block threats in milliseconds, far faster than human analysts. However, automation requires careful safeguards — rate limits on blocking actions, automatic expiration, and human review queues prevent automated systems from causing self-inflicted outages.

🔍 Check Any IP Address

Share this report: