ABUSE.MOM
THREAT REPORT

IP Threat Report
38.248.89.83

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:43:32
First seen: 2026-03-12 12:00:04
Last seen: 2026-03-12 13:00:07
120

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
38.248.89.83
Type
Residential
Country
🇺🇸 United States
City
New York
ISP
Limestone Networks, Inc.
Organization
Limestone Networks
Autonomous System
AS46475 Limestone Networks, Inc.
Hit Count
5
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Σ = 155
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-12 12:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 2 (+50), Danger medium hits: 2 (+20)
2026-03-12 13:00:07
Last malicious request observed
Total score reached: 120/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Limestone Networks, Inc.
AS46475 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

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

🔎 Path Enumeration Protection

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

07

Neighbors in 38.248.89.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 (4)
PortServiceRiskDescription
22SSHLowSecure Shell — common brute force target for remote access
443HTTPSLowHTTPS web server — encrypted web traffic
500UnknownLowService on port 500
7010UnknownLowService on port 7010
DETECTED TECHNOLOGIES
openbsd:openssh:7.6p1
Hostnames: 83-89-248-38.static.reverse.lstn.net
PTR: 83-89-248-38.static.reverse.lstn.net

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
Spamhaus ZEN

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

10

Threat Analysis

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

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

Network traffic from 38.248.89.83, located in New York, United States, operating on the network of Limestone Networks, Inc., has been classified as malicious by our automated threat scoring engine. Our sensors captured 5 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~5 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 121 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 120/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: AS46475

38.248.89.227 (240)38.248.90.25 (195)38.248.95.254 (130)64.31.3.126 (130)38.248.89.70 (120)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Behavioral Analysis vs Signature Detection

Signature-based detection matches known attack patterns but misses novel threats. Behavioral analysis identifies anomalies in request patterns, timing, and volume, catching zero-day attacks that signatures cannot recognize.

🔍 Check Any IP Address

Share this report: