ABUSE.MOM
THREAT REPORT

IP Threat Report
85.108.225.64

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 15:27:08
First seen: 2026-06-12 21:43:00
Last seen: 2026-06-27 22:59:01
60

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
85.108.225.64
Type
Residential
Country
🇹🇷 Turkey
City
Çorlu
ISP
Turk Telekomunikasyon A.S
Organization
Turk Telekomunikasyon A.S
Autonomous System
AS9121 Turk Telekomunikasyon Anonim Sirketi
Hit Count
163
02

Detection Signatures

SignatureDescriptionPointsSeverity
Directory ScanBehavioral anomaly detected by automated analysis+0
Σ = 0
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-06-12 21:43:00
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Directory Scan
2026-06-27 22:59:01
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Turk Telekomunikasyon A.S
AS9121 · 🇹🇷 Turkey

We have detected 155 malicious IPs from this autonomous system.

View all IPs from AS9121 →
06

Recommendations

Actions taken & recommended

  • IP 85.108.225.64 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

⚙️ Defensive Recommendations

Block 85.108.225.64 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

85.108.225.64 has been assigned a threat score of 60/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

📊 Threat Analysis

Network traffic from 85.108.225.64, located in Çorlu, Turkey, operating on the network of Turk Telekomunikasyon A.S, has been classified as malicious by our automated threat scoring engine. Over a period of 15 days, this IP generated 163 malicious requests, averaging approximately 10.9 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Our records show 555 malicious IPs originating from Turkey, positioning it as a major contributor to global threat activity. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇹🇷 Top threats from Turkey

45.136.7.77 (280)45.130.202.6 (255)45.130.202.46 (255)45.130.202.33 (255)45.130.202.21 (255)View all →

🏢 Same network: AS9121

88.241.93.37 (215)78.175.51.241 (165)88.234.4.227 (165)88.227.73.39 (165)78.190.42.244 (140)View all →
12

Security Intelligence

💡 Server-Side Template Injection

SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.

💡 SSH Brute Force Defense

SSH servers face constant brute force attacks targeting common usernames and weak passwords. Key-based authentication, fail2ban, non-standard ports, and IP allowlisting dramatically reduce the attack surface. Monitoring auth logs reveals active campaigns and compromised credentials.

🔍 Check Any IP Address

Share this report: