ABUSE.MOM
THREAT REPORT

IP Threat Report
172.96.90.43

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:51:11
First seen: 2026-03-20 16:00:05
Last seen: 2026-03-21 16: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: 2.

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
172.96.90.43
Type
Residential
Country
🇺🇸 United States
City
Chicago
ISP
Emeigh Investments LLC
Organization
Sprious LLC, Blazing SEO, LLC
Autonomous System
AS20001 Charter Communications Inc
Hit Count
2
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-03-20 16:00:05
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-21 16: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

Emeigh Investments LLC
AS20001 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

08

Open Ports & Services

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

OPEN PORTS (2)
PortServiceRiskDescription
4444UnknownLowService on port 4444
8000UnknownLowService on port 8000
KNOWN VULNERABILITIES (CVE) (27)
CVE IDLink
CVE-2024-25111NVD →
CVE-2023-5824NVD →
CVE-2023-49288NVD →
CVE-2023-46724NVD →
CVE-2021-31808NVD →
CVE-2024-25617NVD →
CVE-2023-46728NVD →
CVE-2023-46847NVD →
CVE-2024-45802NVD →
CVE-2025-54574NVD →
CVE-2025-62168NVD →
CVE-2021-28651NVD →
CVE-2025-59362NVD →
CVE-2023-49286NVD →
CVE-2021-28662NVD →
CVE-2021-28116NVD →
CVE-2021-31806NVD →
CVE-2023-50269NVD →
CVE-2022-41317NVD →
CVE-2021-28652NVD →
CVE-2024-37894NVD →
CVE-2021-31807NVD →
CVE-2021-46784NVD →
CVE-2023-46846NVD →
CVE-2023-49285NVD →
+2 more

🔴 This host has 27 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:4.14
Hostnames: host-172-96-90-43.static.sprious.com
PTR: host-172-96-90-43.static.sprious.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
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

172.96.90.43 has been assigned a threat score of 105/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

172.96.90.43 is registered in Chicago, United States, operating on the network of Emeigh Investments LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 1 days, this IP generated 2 malicious requests, averaging approximately 2 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 201 flagged addresses, United States represents a significant presence in our threat database. 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: AS20001

147.53.118.71 (205)167.160.78.163 (205)168.91.41.80 (200)138.229.100.203 (200)168.91.41.81 (175)View all →
12

Security Intelligence

💡 Command Injection Techniques

Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.

💡 Responsible Disclosure Ethics

Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.

🔍 Check Any IP Address

Share this report: