ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.224.14

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 09:02:23
First seen: 2026-05-30 02:07:30
Last seen: 2026-05-30 08:58:53
90

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404UA_SUS
01

Geolocation & Classification

IP Address
173.239.224.14
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
116
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 suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 115
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-05-30 02:07:30
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-30 08:58:53
Last malicious request observed
Total score reached: 90/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 173.239.224.14 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.224.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 173.239.224.14 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.224.14: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

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

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

10

Threat Analysis

173.239.224.14 has been assigned a threat score of 90/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

The address 173.239.224.14 originates from an unknown location. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 116 malicious requests, averaging approximately 116 requests per day. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With a threat score of 90/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

11

Related Threats

🇤🇤 Top threats from ??

View all →
12

Security Intelligence

💡 Command Injection Techniques

Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.

💡 Web Application Firewall Strategies

WAFs inspect HTTP traffic to block common attacks but require careful tuning. Overly aggressive rules cause false positives while permissive configurations miss attacks. Modern WAFs combine signature matching with behavioral analysis and machine learning.

🔍 Check Any IP Address

Share this report: