ABUSE.MOM
THREAT REPORT

IP Threat Report
138.68.176.28

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:18:06
First seen: 2026-07-26 04:27:46
Last seen: 2026-07-30 00:08:32
85

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODUA_SUS
01

Geolocation & Classification

IP Address
138.68.176.28
Type
Hosting
Country
🇬🇧 United Kingdom
City
Slough
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
203
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 8/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
POST seenBehavioral anomaly detected by automated analysis+8
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 128
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-26 04:27:46
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 8/2s (+35), Danger medium hits: 2 (+20), Danger strong hits: 2 (+50)
2026-07-30 00:08:32
Last malicious request observed
Total score reached: 85/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇬🇧 United Kingdom
06

Recommendations

Actions taken & recommended

  • IP 138.68.176.28 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 138.68.176.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 138.68.176.28.

🤖 User-Agent Anomaly Defense

IP 138.68.176.28 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

07

Neighbors in 138.68.176.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
bl.blocklist.de
✓ Clean
cbl.abuseat.org

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

10

Threat Analysis

138.68.176.28 has been assigned a threat score of 85/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:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 138.68.176.28, geolocated to Slough, United Kingdom, operating on the network of DigitalOcean, LLC, as a source of suspicious network activity. The address has been active for 3 days in our monitoring system, producing 203 flagged requests at a rate of ~67.7/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. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. With 109 flagged addresses, United Kingdom represents a significant presence in our threat database. A threat score of 85/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.

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 Kingdom

104.28.240.60 (340)104.28.208.60 (340)91.230.225.239 (305)91.230.225.147 (305)185.92.25.78 (305)View all →

🏢 Same network: AS14061

157.230.45.147 (265)152.42.180.126 (263)137.184.112.33 (255)68.183.5.181 (248)152.42.242.135 (230)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.

💡 Rate Limiting and Throttling Strategies

Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.

🔍 Check Any IP Address

Share this report: