ABUSE.MOM
THREAT REPORT

IP Threat Report
193.32.249.165

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 09:10:10
First seen: 2026-09-21 15:00:37
Last seen: 2026-10-25 04:06:33
145

⛔ Verdict: BLOCK

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

BOT_UABURSTMETHODRATIO_404REDIRECT_PROBEREFERERUA_CHANGEDspam
01

Geolocation & Classification

IP Address
193.32.249.165
Type
Hosting
Country
🇳🇱 Netherlands
City
Amsterdam
ISP
31173 Services AB
Organization
31173 Services Netherlands
Autonomous System
AS39351 31173 Services AB
Hit Count
512
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 5/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
spam:no_js_checkSpam/malware keywords in request content+0
Σ = 153
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-09-21 15:00:37
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 5/2s (+35), Foreign referer (+10)
2026-10-25 04:06:33
Last malicious request observed
Total score reached: 145/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

31173 Services AB
AS39351 · 🇳🇱 Netherlands

We have detected 12 malicious IPs from this autonomous system.

View all IPs from AS39351 →
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

IP 193.32.249.165 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

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

🤖 User-Agent Anomaly Defense

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

📧 Content Abuse Prevention

IP 193.32.249.165 is flooding forms with spam. Implement time-based tokens and block IPs submitting more than 5 forms per hour.

07

Neighbors in 193.32.249.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
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

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

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 193.32.249.165 has been traced to Amsterdam, Netherlands, operating on the network of 31173 Services AB. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 33-day observation window, we recorded 512 hostile requests from this IP — roughly 15.5 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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 2,848 flagged addresses, Netherlands represents a major presence in our threat database. At 145/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 Netherlands

91.92.43.144 (358)91.92.43.186 (358)91.92.43.190 (358)91.92.43.157 (358)91.92.43.153 (358)View all →

🏢 Same network: AS39351

193.32.248.139 (175)193.32.126.153 (150)185.65.134.202 (110)193.32.249.246 (110)185.65.134.238 (110)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: