ABUSE.MOM
THREAT REPORT

IP Threat Report
35.217.34.238

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 02:15:25
First seen: 2026-07-09 07:47:15
Last seen: 2026-07-26 04:05:46
105

⛔ Verdict: BLOCK

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

BURSTREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
35.217.34.238
Type
Hosting
Country
🇫🇮 Finland
City
Lappeenranta
ISP
Google LLC
Organization
Google Cloud (europe-north1)
Autonomous System
AS15169 Google LLC
Hit Count
362
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 10/10sAbnormally fast request rate — automated scanning+35
Burst 5/2sAbnormally fast request rate — automated scanning+35
Burst 6/2sAbnormally fast request rate — automated scanning+35
Burst 8/2sAbnormally fast request rate — automated scanning+35
Burst 9/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 210
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-07-09 07:47:15
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 10/10s (+35), Burst 5/2s (+35), Burst 6/2s (+35)
2026-07-26 04:05:46
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS15169 · 🇫🇮 Finland
06

Recommendations

Actions taken & recommended

  • IP 35.217.34.238 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.217.34.238.

🤖 User-Agent Anomaly Defense

IP 35.217.34.238 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
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

35.217.34.238 has been assigned a threat score of 105/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 35.217.34.238 to malicious activity originating from Lappeenranta, Finland, operating on the network of Google LLC. The address has been under observation since its initial detection. Our sensors captured 362 malicious requests from this address across a 16-day span, reflecting a sustained attack cadence of ~22.6 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. With a threat score of 105/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 Finland

View all →

🏢 Same network: AS15169

74.125.215.40 (145)74.125.215.39 (145)74.125.215.38 (135)74.125.77.24 (80)66.249.80.225 (75)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.

💡 Container Security Challenges

Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.

🔍 Check Any IP Address

Share this report: