ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.214.164

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 09:22:16
First seen: 2026-04-09 13:00:06
Last seen: 2026-05-24 09:59:54
255

⛔ Verdict: BLOCK

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

BOT_UABURSTDANGER_PATHRATIO_404UA_CHANGEDUA_SUS
01

Geolocation & Classification

IP Address
173.239.214.164
Type
Residential
Country
🇺🇸 United States
City
Edison
ISP
LogicWeb Inc
Organization
Unknown
Autonomous System
AS62240 Clouvider
Hit Count
61
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 23 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 24 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 80 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 83 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 50Medium-risk: admin panels, config files+60
Danger medium hits: 970Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 127High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 378High-risk paths: shells, RCE vectors, exploits+100
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 665
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-04-09 13:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst: 23 req / 2s (+35)
2026-05-24 09:59:54
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

LogicWeb Inc
AS62240 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

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

🌊 Traffic Flood Defense

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

🤖 User-Agent Anomaly Defense

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

07

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

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

10

Threat Analysis

173.239.214.164 has been assigned a threat score of 255/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

173.239.214.164 is registered in Edison, United States, operating on the network of LogicWeb Inc. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 44 days in our monitoring system, producing 61 flagged requests at a rate of ~1.4/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. United States currently accounts for 210 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 255/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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: AS62240

92.119.36.49 (330)45.147.244.27 (313)98.159.37.212 (305)92.119.36.41 (305)92.119.36.92 (305)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.

💡 Rate Limiting and Throttling Strategies

Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.

🔍 Check Any IP Address

Share this report: