ABUSE.MOM
THREAT REPORT

IP Threat Report
174.138.72.220

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-08-23 23:20:38
First seen: 2026-08-21 20:09:29
Last seen: 2026-08-23 00:38:31
68

⛔ Verdict: BLOCK

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

BOT_UAMETHODREDIRECT_PROBE
01

Geolocation & Classification

IP Address
174.138.72.220
Type
Hosting
Country
🇺🇸 United States
City
Clifton
ISP
DigitalOcean, LLC
Organization
Digital Ocean
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
41
02

Detection Signatures

SignatureDescriptionPointsSeverity
POST seenBehavioral anomaly detected by automated analysis+8
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA bot: pythonKnown bot/crawler User-Agent detected+40
Σ = 68
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-08-21 20:09:29
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
POST seen (+8), Probe 302→404 (+20), UA bot: python (+40)
2026-08-23 00:38:31
Last malicious request observed
Total score reached: 68/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 174.138.72.220 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

🔎 Path Enumeration Protection

Block scanning from 174.138.72.220: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 Bot Detection

Address UA spoofing from 174.138.72.220: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

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
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

174.138.72.220 has been assigned a threat score of 68/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 174.138.72.220 to malicious activity originating from Clifton, United States, operating on the network of DigitalOcean, LLC. The address has been under observation since its initial detection. Our sensors captured 41 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~41 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 116 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 68/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

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)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS14061

152.42.236.252 (273)157.230.45.147 (265)152.42.180.126 (263)139.59.247.31 (263)157.245.198.244 (263)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Machine Learning in Threat Detection

Machine learning models analyze vast amounts of network traffic to identify attack patterns invisible to rule-based systems. Supervised models classify known attack types while unsupervised models detect anomalies that may indicate novel threats.

🔍 Check Any IP Address

Share this report: