ABUSE.MOM
THREAT REPORT

IP Threat Report
151.245.166.4

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:05:25
First seen: 2026-02-17 17:25:06
Last seen: 2026-03-01 06:00:06
75

⛔ Verdict: BLOCK

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

DANGER_PATHREDIRECT_PROBEREFERERRATIO_404
01

Geolocation & Classification

IP Address
151.245.166.4
Type
Residential
Country
🇺🇸 United States
City
Seattle
ISP
Sprious LLC
Organization
Unknown
Autonomous System
AS64267 Sprious LLC
Hit Count
5
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 2Medium-risk: admin panels, config files+20
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Danger medium hits: 3Medium-risk: admin panels, config files+30
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Σ = 95
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-17 17:25:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 2 (+20), Probe pattern 302->404 same path (+20), Foreign referer seen (+10)
2026-03-01 06:00:06
Last malicious request observed
Total score reached: 75/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 151.245.166.4 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 151.245.166.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 151.245.166.4: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

07

Neighbors in 151.245.166.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 (3)
PortServiceRiskDescription
4444UnknownLowService on port 4444
8000UnknownLowService on port 8000
60000UnknownLowService on port 60000
KNOWN VULNERABILITIES (CVE) (27)
CVE IDLink
CVE-2021-33620NVD →
CVE-2024-25111NVD →
CVE-2021-28116NVD →
CVE-2025-62168NVD →
CVE-2021-31807NVD →
CVE-2023-5824NVD →
CVE-2023-49285NVD →
CVE-2025-54574NVD →
CVE-2021-31806NVD →
CVE-2021-46784NVD →
CVE-2021-28652NVD →
CVE-2022-41317NVD →
CVE-2023-46847NVD →
CVE-2023-49288NVD →
CVE-2021-28662NVD →
CVE-2023-46724NVD →
CVE-2023-50269NVD →
CVE-2024-45802NVD →
CVE-2024-37894NVD →
CVE-2024-25617NVD →
CVE-2022-41318NVD →
CVE-2023-49286NVD →
CVE-2021-31808NVD →
CVE-2023-46846NVD →
CVE-2025-59362NVD →
+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

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

151.245.166.4 has been assigned a threat score of 75/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Network traffic from 151.245.166.4, located in Seattle, United States, operating on the network of Sprious LLC, has been classified as malicious by our automated threat scoring engine. Our sensors captured 5 malicious requests from this address across a 11-day span, reflecting a sustained attack cadence of ~0.5 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. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. United States currently accounts for 205 blocked IPs in our database, making it a significant source of malicious traffic. At 75/100, this IP warrants immediate defensive action.

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

💡 Directory Traversal Attacks

Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.

💡 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.

🔍 Check Any IP Address

Share this report: