ABUSE.MOM
THREAT REPORT

IP Threat Report
167.160.67.246

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 21:05:08
First seen: 2026-05-09 06:00:08
Last seen: 2026-05-09 06:00:08
105

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
167.160.67.246
Type
Residential
Country
🇺🇸 United States
City
Dallas
ISP
Sprious LLC
Organization
Blazing SEO, LLC
Autonomous System
AS64267 Sprious LLC
Hit Count
1
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
Σ = 105
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-05-09 06: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-05-09 06:00:08
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

Sprious LLC
AS64267 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 167.160.67.246 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 167.160.67.246 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 (3)
PortServiceRiskDescription
4444UnknownLowService on port 4444
8000UnknownLowService on port 8000
60000UnknownLowService on port 60000
KNOWN VULNERABILITIES (CVE) (30)
CVE IDLink
CVE-2023-49285NVD →
CVE-2026-33515NVD →
CVE-2023-46847NVD →
CVE-2021-46784NVD →
CVE-2021-31806NVD →
CVE-2023-49286NVD →
CVE-2025-62168NVD →
CVE-2024-45802NVD →
CVE-2023-46846NVD →
CVE-2024-37894NVD →
CVE-2021-28662NVD →
CVE-2026-33526NVD →
CVE-2026-32748NVD →
CVE-2025-54574NVD →
CVE-2022-41317NVD →
CVE-2023-49288NVD →
CVE-2021-28116NVD →
CVE-2022-41318NVD →
CVE-2024-25617NVD →
CVE-2023-46728NVD →
CVE-2021-31807NVD →
CVE-2021-33620NVD →
CVE-2021-28651NVD →
CVE-2025-59362NVD →
CVE-2021-28652NVD →
+5 more

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

DETECTED TECHNOLOGIES
squid-cache:squid:4.14
Hostnames: host-167-160-67-246.static.sprious.com
PTR: host-167-160-67-246.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-1.uceprotect.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.sorbs.net
✓ 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

167.160.67.246 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 167.160.67.246 to malicious activity originating from Dallas, United States, operating on the network of Sprious LLC. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 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. Our records show 200 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: 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

💡 Cross-Site Scripting (XSS) Attacks

XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.

💡 GraphQL Security Risks

GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.

🔍 Check Any IP Address

Share this report: