ABUSE.MOM
THREAT REPORT

IP Threat Report
192.126.213.234

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 17:32:18
First seen: 2026-02-26 00:00:08
Last seen: 2026-03-18 18:00:04
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.213.234
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: 6Medium-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: 4Medium-risk: admin panels, config files+40
Σ = 145
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-02-26 00:00:08
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 6 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-03-18 18:00:04
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.213.234 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.213.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.213.234: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

07

Neighbors in 192.126.213.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
3128UnknownLowService on port 3128
8000UnknownLowService on port 8000
8080HTTP-AltLowHTTP alternative port — often used for admin panels or proxies
8800UnknownLowService on port 8800
KNOWN VULNERABILITIES (CVE) (56)
CVE IDLink
CVE-2021-28116NVD →
CVE-2023-46847NVD →
CVE-2019-12522NVD →
CVE-2021-31807NVD →
CVE-2024-37894NVD →
CVE-2018-19131NVD →
CVE-2020-25097NVD →
CVE-2025-59362NVD →
CVE-2024-45802NVD →
CVE-2020-15811NVD →
CVE-2019-18678NVD →
CVE-2023-46728NVD →
CVE-2018-1000024NVD →
CVE-2023-49288NVD →
CVE-2019-12529NVD →
CVE-2016-10003NVD →
CVE-2020-8449NVD →
CVE-2021-28652NVD →
CVE-2019-18676NVD →
CVE-2019-12520NVD →
CVE-2019-13345NVD →
CVE-2021-28651NVD →
CVE-2020-8517NVD →
CVE-2021-33620NVD →
CVE-2025-62168NVD →
+31 more

🔴 This host has 56 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.

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

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

10

Threat Analysis

192.126.213.234 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

The address 192.126.213.234 originates from Seattle, United States, operating on the network of EliteWork LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 20 days in our monitoring system, producing 3 flagged requests at a rate of ~0.2/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. United States currently accounts for 138 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 105/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: 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

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 WebSocket Security Considerations

WebSocket connections bypass traditional HTTP security controls, creating opportunities for cross-site WebSocket hijacking, denial of service, and data injection. Proper origin validation, authentication, and message rate limiting are essential for secure WebSocket implementations.

🔍 Check Any IP Address

Share this report: