ABUSE.MOM
THREAT REPORT

IP Threat Report
192.126.163.37

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 17:32:18
First seen: 2026-03-30 19:00:05
Last seen: 2026-04-14 06:00:05
105

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
192.126.163.37
Type
Residential
Country
🇺🇸 United States
City
Seattle
ISP
EliteWork LLC
Organization
BigTip, Inc.
Autonomous System
AS397731 EliteWork LLC
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 10Medium-risk: admin panels, config files+60
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: 6Medium-risk: admin panels, config files+60
Σ = 165
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-30 19:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 10 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-04-14 06:00:05
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

EliteWork LLC
AS397731 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

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

07

Neighbors in 192.126.163.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 (6)
PortServiceRiskDescription
3128UnknownLowService on port 3128
8000UnknownLowService on port 8000
8080HTTP-AltLowHTTP alternative port — often used for admin panels or proxies
8800UnknownLowService on port 8800
21242UnknownLowService on port 21242
52931UnknownLowService on port 52931
KNOWN VULNERABILITIES (CVE) (56)
CVE IDLink
CVE-2021-33620NVD →
CVE-2019-18676NVD →
CVE-2019-12526NVD →
CVE-2020-24606NVD →
CVE-2021-28116NVD →
CVE-2018-19132NVD →
CVE-2018-1000027NVD →
CVE-2025-59362NVD →
CVE-2020-15810NVD →
CVE-2019-12520NVD →
CVE-2020-8450NVD →
CVE-2020-15811NVD →
CVE-2024-37894NVD →
CVE-2023-49285NVD →
CVE-2021-31806NVD →
CVE-2019-18677NVD →
CVE-2025-54574NVD →
CVE-2019-12521NVD →
CVE-2019-13345NVD →
CVE-2018-1000024NVD →
CVE-2020-15049NVD →
CVE-2021-31807NVD →
CVE-2019-12524NVD →
CVE-2020-14058NVD →
CVE-2018-19131NVD →
+31 more

🔴 Security scanning identified 56 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.

DETECTED TECHNOLOGIES
squid-cache:squid:3.5.20

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
dnsbl-1.uceprotect.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

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

Path Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 192.126.163.37 to malicious activity originating from Seattle, United States, operating on the network of EliteWork LLC. The address has been under observation since its initial detection. Our sensors captured 3 malicious requests from this address across a 14-day span, reflecting a sustained attack cadence of ~0.2 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 138 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 105/100 places this address in the top tier of severity. Block and investigate any historical connections.

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

192.126.214.37 (105)192.126.215.254 (105)192.126.215.130 (105)192.126.159.228 (105)192.126.215.30 (105)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.

💡 Server-Side Template Injection

SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.

🔍 Check Any IP Address

Share this report: