ABUSE.MOM
THREAT REPORT

IP Threat Report
139.180.225.26

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-14 14:53:08
First seen: 2026-09-13 17:45:44
Last seen: 2026-09-14 14:31:56
95

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
139.180.225.26
Type
Hosting
Country
🇺🇸 United States
City
New York
ISP
Sprious LLC, Blazing SEO, LLC
Organization
Emeigh Investments LLC
Autonomous System
AS64267 Sprious LLC
Hit Count
47
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 5Medium-risk: admin panels, config files+50
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 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-09-13 17:45:44
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 5 (+50), Foreign referer (+10)
2026-09-14 14:31:56
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, Blazing SEO, LLC
AS64267 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

07

Neighbors in 139.180.225.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
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

139.180.225.26 has been assigned a threat score of 95/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

Network traffic from 139.180.225.26, located in New York, United States, operating on the network of Sprious LLC, Blazing SEO, LLC, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 47 malicious requests, averaging approximately 47 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 180 flagged addresses, United States represents a significant presence in our threat database. A score of 95/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇺🇸 Top threats from United States

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

🏢 Same network: AS64267

147.92.55.222 (200)216.180.104.166 (165)148.59.185.188 (140)147.92.55.249 (140)216.41.233.61 (140)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.

💡 Server-Side Template Injection

SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.

🔍 Check Any IP Address

Share this report: