
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 33/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 33/2s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer | Referer from unrelated external domain | +10 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 174.219.104.58.
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
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:
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.
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.
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.