ABUSE.MOM
THREAT REPORT

IP Threat Report
167.160.70.247

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-31 06:59:29
First seen: 2026-07-12 10:53:38
Last seen: 2026-07-31 06:48:02
95

⛔ Verdict: BLOCK

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

DANGER_PATHREDIRECT_PROBEREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
167.160.70.247
Type
VPN
Country
🇺🇸 United States
City
Los Angeles
ISP
Sprious LLC
Organization
Blazing SEO, LLC
Autonomous System
AS64267 Sprious LLC
Hit Count
634
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 4Medium-risk: admin panels, config files+40
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 115
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-07-12 10:53:38
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 2 (+20), Danger medium hits: 4 (+40), Foreign referer (+10)
2026-07-31 06:48:02
Last malicious request observed
Total score reached: 95/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.70.247 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 167.160.70.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 167.160.70.247 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 Bot Detection

Address UA spoofing from 167.160.70.247: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 167.160.70.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
b.barracudacentral.org
✓ Clean
bl.blocklist.de

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

10

Threat Analysis

167.160.70.247 has been assigned a threat score of 95/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 167.160.70.247 to malicious activity originating from Los Angeles, United States, operating on the network of Sprious LLC. The address has been under observation since its initial detection. During its 18-day observation window, we recorded 634 hostile requests from this IP — roughly 35.2 per day on average. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 140 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 95/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS64267

147.92.55.222 (200)139.180.228.230 (130)216.41.235.8 (130)216.41.233.225 (130)147.92.54.134 (130)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.

💡 Cloud Infrastructure Abuse

Cloud platforms provide attackers with elastic, disposable infrastructure. Free tier accounts, stolen credit cards, and compromised cloud credentials enable rapid deployment of attack infrastructure that can scale to millions of requests and disappear within hours.

🔍 Check Any IP Address

Share this report: