ABUSE.MOM
THREAT REPORT

IP Threat Report
170.168.175.156

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 05:54:22
First seen: 2026-04-03 23:00:07
Last seen: 2026-04-03 23: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.175.156
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: 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: 9 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-03 23: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-03 23: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.175.156 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.156 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🌊 Traffic Flood Defense

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

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

10

Threat Analysis

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

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

Network traffic from 170.168.175.156, located in Wałcz, Poland, operating on the network of Alex Largman, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. 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.96.250 (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.96.250 (313)170.168.175.34 (313)122.8.95.61 (268)88.218.45.194 (268)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 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: