ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.218.167

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:12:42
First seen: 2026-05-31 17:53:51
Last seen: 2026-06-07 20:03:22
100

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
173.239.218.167
Type
Unknown
Country
🇺🇸 United States
City
Los Angeles
ISP
LogicWeb Inc
Organization
LogicWeb Inc
Autonomous System
Unknown
Hit Count
246
02

Detection Signatures

SignatureDescriptionPointsSeverity
Directory ScanBehavioral anomaly detected by automated analysis+0
Σ = 0
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-31 17:53:51
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Directory Scan
2026-06-07 20:03:22
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

⚙️ Defensive Recommendations

Block 173.239.218.167 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

07

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

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

10

Threat Analysis

173.239.218.167 has been assigned a threat score of 100/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

📊 Threat Analysis

The address 173.239.218.167 originates from Los Angeles, United States, operating on the network of LogicWeb Inc. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 246 malicious requests from this address across a 7-day span, reflecting a sustained attack cadence of ~35.1 requests per day. With 151 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 100/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 United States

104.28.246.115 (350)104.28.214.122 (350)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →
12

Security Intelligence

💡 Backup and Recovery Against Ransomware

Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

🔍 Check Any IP Address

Share this report: