ABUSE.MOM
THREAT REPORT

IP Threat Report
134.209.72.177

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 14:08:19
First seen: 2026-02-21 00:05:04
Last seen: 2026-02-21 00:05:04
65

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGED
01

Geolocation & Classification

IP Address
134.209.72.177
Type
Hosting
Country
🇺🇸 United States
City
North Bergen
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: pythonKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Σ = 65
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-02-21 00:05:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: python (+40), UA changed for same IP (+25)
2026-02-21 00:05:04
Last malicious request observed
Total score reached: 65/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 134.209.72.177 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

🤖 Bot Detection

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (2)
PortServiceRiskDescription
22SSHLowSecure Shell — common brute force target for remote access
443HTTPSLowHTTPS web server — encrypted web traffic
KNOWN VULNERABILITIES (CVE) (4)
CVE IDLink
CVE-2023-44487NVD →
CVE-2021-23017NVD →
CVE-2025-23419NVD →
CVE-2021-3618NVD →

🔴 This host has 4 known CVEs associated with its exposed services. Multiple vulnerabilities suggest gaps in patch management. Review each CVE in the NVD database.

DETECTED TECHNOLOGIES
linux:linux_kernelopenbsd:openssh:8.9p1f5:nginx:1.18.0canonical:ubuntu_linux

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

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

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

The address 134.209.72.177 originates from North Bergen, United States, operating on the network of DigitalOcean, LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 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. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. Our records show 128 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS14061

129.212.237.216 (308)168.144.34.140 (295)170.64.203.182 (280)161.35.89.38 (273)64.226.94.117 (273)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 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.

🔍 Check Any IP Address

Share this report: