ABUSE.MOM
THREAT REPORT

IP Threat Report
170.199.228.127

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 05:14:35
First seen: 2026-04-22 16:00:05
Last seen: 2026-04-22 16:00:05
70

⛔ Verdict: BLOCK

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

DANGER_PATHREDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
170.199.228.127
Type
Residential
Country
🇺🇸 United States
City
Los Angeles
ISP
Blazing SEO
Organization
Sprious LLC, Emeigh Investments LLC
Autonomous System
AS20001 Charter Communications Inc
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 4Medium-risk: admin panels, config files+40
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Σ = 70
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-22 16:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 4 (+40), Probe pattern 302->404 same path (+20), Foreign referer seen (+10)
2026-04-22 16:00:05
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Blazing SEO
AS20001 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

07

Neighbors in 170.199.228.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-2023-49286NVD →
CVE-2025-54574NVD →
CVE-2023-46728NVD →
CVE-2025-62168NVD →
CVE-2021-31807NVD →
CVE-2021-31808NVD →
CVE-2021-46784NVD →
CVE-2021-28116NVD →
CVE-2021-28651NVD →
CVE-2024-45802NVD →
CVE-2026-33515NVD →
CVE-2024-37894NVD →
CVE-2021-31806NVD →
CVE-2021-33620NVD →
CVE-2025-59362NVD →
CVE-2023-46846NVD →
CVE-2023-50269NVD →
CVE-2023-49285NVD →
CVE-2022-41318NVD →
CVE-2026-33526NVD →
CVE-2022-41317NVD →
CVE-2023-46724NVD →
CVE-2023-46847NVD →
CVE-2023-49288NVD →
CVE-2024-25111NVD →
+5 more

🔴 This host has 30 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
Hostnames: host-170-199-228-127.static.sprious.com
PTR: host-170-199-228-127.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
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

170.199.228.127 has been assigned a threat score of 70/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

170.199.228.127 is registered in Los Angeles, United States, operating on the network of Blazing SEO. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 208 blocked IPs in our database, making it a significant source of malicious traffic. A threat score of 70/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.

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: AS20001

147.53.118.71 (205)167.160.78.163 (205)168.91.41.80 (200)138.229.100.203 (200)168.91.41.81 (175)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 Patch Management Urgency

The window between vulnerability disclosure and exploitation continues to shrink. Critical CVEs are now exploited within hours of publication. Automated patch management, virtual patching through WAFs, and rapid deployment pipelines are essential for timely remediation.

🔍 Check Any IP Address

Share this report: