ABUSE.MOM
THREAT REPORT

IP Threat Report
64.50.191.32

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 22:53:09
First seen: 2026-04-14 07:00:06
Last seen: 2026-05-07 23:00:15
130

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTREFERER
01

Geolocation & Classification

IP Address
64.50.191.32
Type
Residential
Country
🇺🇸 United States
City
Los Angeles
ISP
BreezeHost
Organization
IPXO
Autonomous System
AS400810 BreezeHost
Hit Count
14
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Burst: 25 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 28 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 165
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-04-14 07:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 2 (+50), Burst: 5 req / 2s (+35), Foreign referer seen (+10)
2026-05-07 23:00:15
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

BreezeHost
AS400810 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 64.50.191.32 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 64.50.191.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 64.50.191.32.

07

Neighbors in 64.50.191.0/24

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

08

Open Ports & Services

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

OPEN PORTS (2)
PortServiceRiskDescription
25SMTPMediumSMTP mail server — can be abused for spam relay
80HTTPLowHTTP web server — standard web traffic
KNOWN VULNERABILITIES (CVE) (26)
CVE IDLink
CVE-2019-11047NVD →
CVE-2019-11050NVD →
CVE-2022-31628NVD →
CVE-2020-7059NVD →
CVE-2020-7067NVD →
CVE-2024-25117NVD →
CVE-2022-31629NVD →
CVE-2020-7060NVD →
CVE-2017-8923NVD →
CVE-2019-11048NVD →
CVE-2020-7063NVD →
CVE-2019-11046NVD →
CVE-2022-4900NVD →
CVE-2020-7069NVD →
CVE-2019-11045NVD →
CVE-2024-3566NVD →
CVE-2020-7070NVD →
CVE-2020-7061NVD →
CVE-2019-11044NVD →
CVE-2020-7062NVD →
CVE-2007-3205NVD →
CVE-2020-7068NVD →
CVE-2020-7064NVD →
CVE-2022-37454NVD →
CVE-2013-2220NVD →
+1 more

🔴 This host has 26 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.

DETECTED TECHNOLOGIES
php:php:7.2.24f5:nginxpostfix:postfix
Hostnames: denvercityagent.cominternetguidepro.com

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
zen.spamhaus.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

64.50.191.32 has been assigned a threat score of 130/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

Network traffic from 64.50.191.32, located in Los Angeles, United States, operating on the network of BreezeHost, has been classified as malicious by our automated threat scoring engine. Our sensors captured 14 malicious requests from this address across a 23-day span, reflecting a sustained attack cadence of ~0.6 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. At 130/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇺🇸 Top threats from United States

64.50.191.33 (95)154.58.229.82 (95)View all →

🏢 Same network: AS400810

95.169.173.40 (130)151.243.143.47 (95)64.50.191.33 (95)154.58.229.82 (95)95.169.173.32 (95)View all →
12

Security Intelligence

💡 Credential Stuffing at Scale

Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.

💡 Behavioral Analysis vs Signature Detection

Signature-based detection matches known attack patterns but misses novel threats. Behavioral analysis identifies anomalies in request patterns, timing, and volume, catching zero-day attacks that signatures cannot recognize.

🔍 Check Any IP Address

Share this report: