ABUSE.MOM
THREAT REPORT

IP Threat Report
174.227.11.160

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-28 14:52:15
First seen: 2026-07-11 01:33:44
Last seen: 2026-07-12 00:57:27
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

IP Address
174.227.11.160
Type
Mobile
Country
🇺🇸 United States
City
Vancouver
ISP
Verizon Business
Organization
Verizon Business
Autonomous System
AS6167 Verizon Business
Hit Count
54
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 58/2sAbnormally fast request rate — automated scanning+35
Burst 59/10sAbnormally 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-11 01:33:44
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 58/2s (+35), Burst 59/10s (+35), Foreign referer (+10)
2026-07-12 00:57:27
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.227.11.160 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

🌊 Traffic Flood Defense

IP 174.227.11.160 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

09

Blacklist Status (DNSBL)

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

✓ Clean
cbl.abuseat.org
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
b.barracudacentral.org
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

174.227.11.160 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

Our monitoring infrastructure has identified 174.227.11.160, geolocated to Vancouver, United States, operating on the network of Verizon Business, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 54 flagged requests at a rate of ~54/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. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Our records show 111 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 80/100, this IP warrants immediate defensive action.

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.204.196.165 (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.

💡 Memory Safety and Buffer Overflows

Buffer overflow vulnerabilities remain relevant in C/C++ applications despite decades of mitigation efforts. Modern protections like ASLR, stack canaries, and DEP reduce exploitability but determined attackers continue finding bypass techniques.

🔍 Check Any IP Address

Share this report: