ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.211.28

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-29 12:55:03
First seen: 2026-05-27 14:39:56
Last seen: 2026-05-29 12:53:03
75

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404UA_SUS
01

Geolocation & Classification

IP Address
173.239.211.28
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
220
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 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-27 14:39:56
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger medium hits: 1 (+10), Danger strong hits: 1 (+25)
2026-05-29 12:53:03
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.211.28 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.211.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

Block scanning from 173.239.211.28: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 Bot Detection

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

07

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

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

10

Threat Analysis

173.239.211.28 has been assigned a threat score of 75/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

173.239.211.28 is registered in an unknown location. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 220 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~220 requests per day. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. The score of 75/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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 Cache Poisoning Attacks

Cache poisoning manipulates web cache behavior to serve malicious content to other users. By identifying unkeyed inputs that influence cached responses, attackers can inject JavaScript, redirect users, or cause denial of service at scale through the cache infrastructure.

🔍 Check Any IP Address

Share this report: