ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.254.41

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:06:29
First seen: 2026-05-28 21:48:24
Last seen: 2026-05-30 07:35:26
75

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
173.239.254.41
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
44
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: 2High-risk paths: shells, RCE vectors, exploits+50
Σ = 75
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-28 21:48:24
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: 2 (+50)
2026-05-30 07:35:26
Last malicious request observed
Total score reached: 75/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

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

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

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

10

Threat Analysis

173.239.254.41 has been assigned a threat score of 75/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

IP address 173.239.254.41 has been traced to an unknown location. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 1-day observation window, we recorded 44 hostile requests from this IP — roughly 44 per day on average. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. At 75/100, this IP warrants immediate defensive action.

11

Related Threats

🇤🇤 Top threats from ??

View all →
12

Security Intelligence

💡 Cross-Site Scripting (XSS) Attacks

XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.

💡 CAPTCHA and Bot Detection

CAPTCHAs remain a primary bot defense but face increasing bypass rates from AI-powered solvers. Modern alternatives include invisible behavioral analysis, proof-of-work challenges, and device fingerprinting that detect bots without impacting user experience.

🔍 Check Any IP Address

Share this report: