ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.254.175

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-29 16:14:06
First seen: 2026-03-24 00:00:07
Last seen: 2026-05-29 15:33:14
100

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHRATIO_404UA_CHANGEDUA_SUS
01

Geolocation & Classification

IP Address
173.239.254.175
Type
Residential
Country
🇺🇸 United States
City
Seattle
ISP
LogicWeb Inc
Organization
Unknown
Autonomous System
AS206092 F.N.S. HOLDINGS LIMITED
Hit Count
200
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Σ = 180
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-03-24 00:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 1 (+10), Danger strong hits: 1 (+25)
2026-05-29 15:33:14
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

LogicWeb Inc
AS206092 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 173.239.254.175 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 173.239.254.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 173.239.254.175 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 Bot Detection

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

07

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

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

10

Threat Analysis

173.239.254.175 has been assigned a threat score of 100/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 EnumerationUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 173.239.254.175, geolocated to Seattle, United States, operating on the network of LogicWeb Inc, as a source of suspicious network activity. Over a period of 66 days, this IP generated 200 malicious requests, averaging approximately 3 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 149 flagged addresses, United States represents a significant presence in our threat database. A score of 100/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS206092

103.163.220.216 (340)85.203.21.101 (320)85.203.21.157 (310)85.203.21.172 (305)91.217.249.222 (305)View all →
12

Security Intelligence

💡 Brute Force Attack Mechanics

Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.

💡 Directory Traversal Attacks

Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.

🔍 Check Any IP Address

Share this report: