ABUSE.MOM
THREAT REPORT

IP Threat Report
97.230.135.63

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 17:23:12
First seen: 2026-10-20 01:49:56
Last seen: 2026-10-25 04:04:05
60

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
97.230.135.63
Type
Mobile
Country
🇺🇸 United States
City
Charlotte
ISP
Verizon Business
Organization
Verizon Business
Autonomous System
AS6167 Verizon Business
Hit Count
106
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Foreign refererReferer from unrelated external domain+10
Σ = 60
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-10-20 01:49:56
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger strong hits: 1 (+25), Foreign referer (+10)
2026-10-25 04:04:05
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Verizon Business
AS6167 · 🇺🇸 United States

We have detected 69 malicious IPs from this autonomous system.

View all IPs from AS6167 →
06

Recommendations

Actions taken & recommended

  • IP 97.230.135.63 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

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

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

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

10

Threat Analysis

97.230.135.63 has been assigned a threat score of 60/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

The address 97.230.135.63 originates from Charlotte, United States, operating on the network of Verizon Business. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 5-day observation window, we recorded 106 hostile requests from this IP — roughly 21.2 per day on average. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 36,338 flagged addresses, United States represents a major presence in our threat database. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS6167

97.233.90.61 (210)75.215.152.206 (155)166.143.153.13 (150)174.239.85.163 (130)174.200.58.16 (130)View all →
12

Security Intelligence

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

💡 Machine Learning in Threat Detection

Machine learning models analyze vast amounts of network traffic to identify attack patterns invisible to rule-based systems. Supervised models classify known attack types while unsupervised models detect anomalies that may indicate novel threats.

🔍 Check Any IP Address

Share this report: