ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.214.130

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 04:37:20
First seen: 2026-04-15 22:00:08
Last seen: 2026-07-05 04:03:00
130

⛔ Verdict: BLOCK

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

DANGER_PATHUA_SUS
01

Geolocation & Classification

IP Address
173.239.214.130
Type
Unknown
Country
🇺🇸 United States
City
Edison
ISP
LogicWeb Inc
Organization
LogicWeb Inc
Autonomous System
Unknown
Hit Count
1442
02

Detection Signatures

SignatureDescriptionPointsSeverity
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Directory ScanBehavioral anomaly detected by automated analysis+0
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 50
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-04-15 22:00:08
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
DDoS / Flood, Danger medium hits: 1 (+10), Danger strong hits: 1 (+25)
2026-07-05 04:03:00
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

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

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
bl.blocklist.de
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

173.239.214.130 has been assigned a threat score of 130/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:

User-Agent Anomaly

📊 Threat Analysis

IP address 173.239.214.130 has been traced to Edison, United States, operating on the network of LogicWeb Inc. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 80 days in our monitoring system, producing 1,442 flagged requests at a rate of ~18/day. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. United States currently accounts for 151 blocked IPs in our database, making it a significant source of malicious traffic. A score of 130/100 places this address in the top tier of severity. Block and investigate any historical connections.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)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.

💡 SSH Brute Force Defense

SSH servers face constant brute force attacks targeting common usernames and weak passwords. Key-based authentication, fail2ban, non-standard ports, and IP allowlisting dramatically reduce the attack surface. Monitoring auth logs reveals active campaigns and compromised credentials.

🔍 Check Any IP Address

Share this report: