ABUSE.MOM
THREAT REPORT

IP Threat Report
174.227.60.83

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-11 05:30:44
First seen: 2026-08-17 05:14:52
Last seen: 2026-08-23 02:03:58
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

IP Address
174.227.60.83
Type
Mobile
Country
🇺🇸 United States
City
Seattle
ISP
Verizon Business
Organization
Verizon Business
Autonomous System
AS6167 Verizon Business
Hit Count
243
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 56/10sAbnormally fast request rate — automated scanning+35
Burst 56/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-08-17 05:14:52
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 56/10s (+35), Burst 56/2s (+35), Foreign referer (+10)
2026-08-23 02:03:58
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.60.83 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.60.83 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
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

174.227.60.83 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.227.60.83 originates from Seattle, United States, operating on the network of Verizon Business. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 5 days, this IP generated 243 malicious requests, averaging approximately 48.6 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. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. United States currently accounts for 119 blocked IPs in our database, making it a significant source of malicious traffic. A threat score of 80/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.

11

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 →

🏢 Same network: AS6167

166.143.153.13 (150)174.204.195.53 (105)174.216.144.25 (95)97.184.117.102 (85)97.165.91.44 (85)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.

💡 Race Condition Vulnerabilities

Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.

🔍 Check Any IP Address

Share this report: