IP Threat Report
174.247.177.18
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 55/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 56/10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer | Referer from unrelated external domain | +10 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
We have detected 69 malicious IPs from this autonomous system.
Recommendations
Actions taken & recommended
- IP 174.247.177.18 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 174.247.177.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🌊 Traffic Flood Defense
IP 174.247.177.18 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Neighbors in 174.247.177.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
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.
Threat Analysis
174.247.177.18 has been assigned a threat score of 80/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:
📊 Threat Analysis
Network traffic from 174.247.177.18, located in Portland, United States, operating on the network of Verizon Business, has been classified as malicious by our automated threat scoring engine. During its 6-day observation window, we recorded 133 hostile requests from this IP — roughly 22.2 per day on average. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. United States currently accounts for 36,321 blocked IPs in our database, making it a major source of malicious traffic. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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 →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.
💡 GeoIP Blocking Considerations
Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.