ABUSE.MOM
THREAT REPORT

IP Threat Report
139.180.229.139

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 01:18:12
First seen: 2026-04-24 04:00:06
Last seen: 2026-04-24 04:00:06
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
139.180.229.139
Type
Residential
Country
🇺🇸 United States
City
San Francisco
ISP
Sprious LLC, Blazing SEO, LLC
Organization
Emeigh Investments LLC
Autonomous System
AS64267 Sprious LLC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 7Medium-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-04-24 04:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 7 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-04-24 04:00:06
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, Blazing SEO, LLC
AS64267 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 139.180.229.139 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.229.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 139.180.229.139: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

07

Neighbors in 139.180.229.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 (1)
PortServiceRiskDescription
4444UnknownLowService on port 4444
KNOWN VULNERABILITIES (CVE) (30)
CVE IDLink
CVE-2026-33515NVD →
CVE-2021-31806NVD →
CVE-2023-46728NVD →
CVE-2021-28116NVD →
CVE-2022-41318NVD →
CVE-2023-46846NVD →
CVE-2021-31807NVD →
CVE-2025-59362NVD →
CVE-2021-28651NVD →
CVE-2021-31808NVD →
CVE-2023-49288NVD →
CVE-2023-5824NVD →
CVE-2024-25617NVD →
CVE-2024-25111NVD →
CVE-2023-50269NVD →
CVE-2023-49286NVD →
CVE-2021-28652NVD →
CVE-2022-41317NVD →
CVE-2021-28662NVD →
CVE-2026-33526NVD →
CVE-2023-46724NVD →
CVE-2024-45802NVD →
CVE-2024-37894NVD →
CVE-2026-32748NVD →
CVE-2021-33620NVD →
+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-139-180-229-139.static.sprious.com
PTR: host-139-180-229-139.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
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

139.180.229.139 has been assigned a threat score of 105/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 139.180.229.139 to malicious activity originating from San Francisco, United States, operating on the network of Sprious LLC, Blazing SEO, LLC. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 202 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 105/100, this is an extremely high-risk address. All traffic should be considered hostile.

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

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 Content Security Policy Implementation

Content Security Policy headers instruct browsers to restrict resource loading, mitigating XSS and data injection attacks. Properly configured CSP policies prevent inline script execution, restrict iframe embedding, and control which domains can serve content.

🔍 Check Any IP Address

Share this report: