ABUSE.MOM
THREAT REPORT

IP Threat Report
174.219.104.58

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-28 14:52:15
First seen: 2026-07-21 04:20:03
Last seen: 2026-07-26 04:01:24
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

IP Address
174.219.104.58
Type
Mobile
Country
🇺🇸 United States
City
Roanoke
ISP
Verizon Business
Organization
Verizon Business
Autonomous System
AS6167 Verizon Business
Hit Count
316
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 33/10sAbnormally fast request rate — automated scanning+35
Burst 33/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Σ = 80
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-07-21 04:20:03
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 33/10s (+35), Burst 33/2s (+35), Foreign referer (+10)
2026-07-26 04:01:24
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Verizon Business
AS6167 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 174.219.104.58 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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 174.219.104.58.

09

Blacklist Status (DNSBL)

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

✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
b.barracudacentral.org
✓ Clean
zen.spamhaus.org

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

10

Threat Analysis

174.219.104.58 has been assigned a threat score of 80/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:

Request Flooding

📊 Threat Analysis

The address 174.219.104.58 originates from Roanoke, United States, operating on the network of Verizon Business. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 316 malicious requests from this address across a 4-day span, reflecting a sustained attack cadence of ~79 requests per day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 111 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

11

Related Threats

🇺🇸 Top threats from United States

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

🏢 Same network: AS6167

174.204.195.53 (105)174.216.144.25 (95)174.224.91.232 (80)174.236.224.31 (80)174.227.11.160 (80)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

🔍 Check Any IP Address

Share this report: