ABUSE.MOM
THREAT REPORT

IP Threat Report
170.168.96.250

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 05:54:22
First seen: 2026-04-26 08:00:07
Last seen: 2026-04-26 08:00:07
313

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGEDDANGER_PATHBURSTREFERERMETHOD
01

Geolocation & Classification

IP Address
170.168.96.250
Type
Hosting
Country
🇵🇱 Poland
City
Cianowice Duże
ISP
Alex Largman
Organization
Fine Group Servers Solutions LLC
Autonomous System
AS59651 AS QualityNetwork
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: javaKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 20High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 14Medium-risk: admin panels, config files+60
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 24 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 313
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-26 08:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: java (+40), UA changed for same IP (+25), Danger strong hits: 20 (+100)
2026-04-26 08:00:07
Last malicious request observed
Total score reached: 313/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.96.250 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.96.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

Address UA spoofing from 170.168.96.250: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 170.168.96.250.

07

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

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

10

Threat Analysis

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

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

IP address 170.168.96.250 has been traced to Cianowice Duże, Poland, operating on the network of Alex Largman. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. 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 (User-Agent Anomaly and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. With a threat score of 313/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 Poland

170.168.175.156 (313)170.168.175.34 (313)170.168.175.136 (220)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.175.34 (313)122.8.95.61 (268)88.218.45.194 (268)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Deepfake Technology in Social Engineering

Deepfake audio and video enable convincing impersonation of executives and trusted individuals. Real-time voice cloning has been used in successful fraud campaigns, adding a new dimension to social engineering that traditional security training does not address.

🔍 Check Any IP Address

Share this report: