ABUSE.MOM
THREAT REPORT

IP Threat Report
170.168.175.136

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:58:40
First seen: 2026-04-20 04:00:06
Last seen: 2026-04-20 04:00:06
220

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHRATIO_404BURSTREFERER
01

Geolocation & Classification

IP Address
170.168.175.136
Type
Hosting
Country
🇵🇱 Poland
City
Wałcz
ISP
Alex Largman
Organization
Fine Group Servers Solutions LLC
Autonomous System
AS59651 AS QualityNetwork
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: curlKnown bot/crawler User-Agent detected+40
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 2Medium-risk: admin panels, config files+20
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 220
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-04-20 04:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: curl (+40), Danger strong hits: 5 (+100), Danger medium hits: 2 (+20)
2026-04-20 04:00:06
Last malicious request observed
Total score reached: 220/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Alex Largman
AS59651 · 🇵🇱 Poland
06

Recommendations

Actions taken & recommended

  • IP 170.168.175.136 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 170.168.175.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 User-Agent Anomaly Defense

IP 170.168.175.136 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🔎 Path Enumeration Protection

Block scanning from 170.168.175.136: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Traffic Flood Defense

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

07

Neighbors in 170.168.175.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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

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

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

The address 170.168.175.136 originates from Wałcz, Poland, operating on the network of Alex Largman. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. A score of 220/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 Poland

170.168.175.156 (313)170.168.96.250 (313)170.168.175.34 (313)170.168.96.46 (160)170.168.175.227 (70)View all →

🏢 Same network: AS59651

5.181.169.192 (313)170.168.175.156 (313)170.168.96.250 (313)170.168.175.34 (313)122.8.95.61 (268)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 IPv6 Scanning Challenges

The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.

🔍 Check Any IP Address

Share this report: