ABUSE.MOM
THREAT REPORT

IP Threat Report
165.22.174.74

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 05:50:32
First seen: 2026-10-20 03:30:26
Last seen: 2026-10-25 04:05:08
170

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

IP Address
165.22.174.74
Type
Hosting
Country
🇺🇸 United States
City
Santa Clara
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
82
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 15/10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Σ = 170
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-10-20 03:30:26
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 14/2s (+35), Burst 15/10s (+35), Danger strong hits: 4 (+100)
2026-10-25 04:05:08
Last malicious request observed
Total score reached: 170/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇺🇸 United States

We have detected 4068 malicious IPs from this autonomous system.

View all IPs from AS14061 →
06

Recommendations

Actions taken & recommended

  • IP 165.22.174.74 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 165.22.174.0/24
  • 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 165.22.174.74.

07

Neighbors in 165.22.174.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

165.22.174.74 has been assigned a threat score of 170/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 165.22.174.74, geolocated to Santa Clara, United States, operating on the network of DigitalOcean, LLC, as a source of suspicious network activity. The address has been active for 5 days in our monitoring system, producing 82 flagged requests at a rate of ~16.4/day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 36,224 malicious IPs originating from United States, positioning it as a major contributor to global threat activity. A score of 170/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

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: AS14061

168.144.130.251 (280)142.93.195.73 (275)152.42.236.252 (273)165.22.77.209 (273)46.101.208.236 (273)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.

💡 Cross-Site Scripting (XSS) Attacks

XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.

🔍 Check Any IP Address

Share this report: