ABUSE.MOM
THREAT REPORT

IP Threat Report
66.146.238.33

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 02:33:21
First seen: 2026-03-23 23:00:05
Last seen: 2026-03-23 23:00:05
70

⛔ Verdict: BLOCK

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

DANGER_PATHREDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
66.146.238.33
Type
Residential
Country
🇺🇸 United States
City
Secaucus
ISP
Sprious LLC
Organization
Blazing SEO, LLC
Autonomous System
AS64267 Sprious LLC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 4Medium-risk: admin panels, config files+40
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Σ = 70
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-23 23:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 4 (+40), Probe pattern 302->404 same path (+20), Foreign referer seen (+10)
2026-03-23 23:00:05
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Sprious LLC
AS64267 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

07

Neighbors in 66.146.238.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 (2)
PortServiceRiskDescription
4444UnknownLowService on port 4444
8000UnknownLowService on port 8000
KNOWN VULNERABILITIES (CVE) (27)
CVE IDLink
CVE-2021-33620NVD →
CVE-2021-28662NVD →
CVE-2022-41318NVD →
CVE-2023-46728NVD →
CVE-2021-31806NVD →
CVE-2024-25617NVD →
CVE-2025-54574NVD →
CVE-2021-31807NVD →
CVE-2023-49286NVD →
CVE-2023-50269NVD →
CVE-2023-49288NVD →
CVE-2023-5824NVD →
CVE-2023-46846NVD →
CVE-2023-49285NVD →
CVE-2021-28651NVD →
CVE-2023-46847NVD →
CVE-2022-41317NVD →
CVE-2021-46784NVD →
CVE-2025-59362NVD →
CVE-2021-28652NVD →
CVE-2021-28116NVD →
CVE-2024-45802NVD →
CVE-2025-62168NVD →
CVE-2024-37894NVD →
CVE-2024-25111NVD →
+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-66-146-238-33.static.sprious.com
PTR: host-66-146-238-33.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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

66.146.238.33 has been assigned a threat score of 70/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

The address 66.146.238.33 originates from Secaucus, United States, operating on the network of Sprious LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 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. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 202 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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

66.146.236.62 (200)216.213.28.68 (200)192.171.87.62 (200)162.244.145.212 (180)199.34.84.33 (180)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 Race Condition Vulnerabilities

Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.

🔍 Check Any IP Address

Share this report: