ABUSE.MOM
THREAT REPORT

IP Threat Report
23.19.248.66

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:46:51
First seen: 2026-03-19 01:00:06
Last seen: 2026-04-15 23:00:07
110

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
23.19.248.66
Type
Hosting
Country
🇺🇸 United States
City
Seattle
ISP
Leaseweb USA, Inc.
Organization
LeaseWeb USA, Inc. Seattle
Autonomous System
AS396190 Leaseweb USA, Inc.
Hit Count
40
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 2Medium-risk: admin panels, config files+20
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Danger medium hits: 4Medium-risk: admin panels, config files+40
Danger medium hits: 8Medium-risk: admin panels, config files+60
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Σ = 190
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-03-19 01:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 2 (+20), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-04-15 23:00:07
Last malicious request observed
Total score reached: 110/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Leaseweb USA, Inc.
AS396190 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 23.19.248.66 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 23.19.248.0/24
  • 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 23.19.248.66 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 Bot Detection

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

07

Neighbors in 23.19.248.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (5)
PortServiceRiskDescription
80HTTPLowHTTP web server — standard web traffic
4444UnknownLowService on port 4444
7777UnknownLowService on port 7777
12345UnknownLowService on port 12345
55555UnknownLowService on port 55555
Hostnames: letters.realtimestocknewsline.com
PTR: letters.realtimestocknewsline.com

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

23.19.248.66 has been assigned a threat score of 110/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 EnumerationUser-Agent Anomaly

📊 Threat Analysis

The address 23.19.248.66 originates from Seattle, United States, operating on the network of Leaseweb USA, Inc.. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 27-day observation window, we recorded 40 hostile requests from this IP — roughly 1.5 per day on average. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. With 148 flagged addresses, United States represents a significant presence in our threat database. At 110/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

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

23.19.248.191 (130)23.19.248.148 (130)23.106.16.84 (130)23.106.16.209 (130)23.19.248.58 (110)View all →
12

Security Intelligence

💡 Remote Code Execution (RCE)

RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.

💡 GraphQL Security Risks

GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.

🔍 Check Any IP Address

Share this report: