IP Threat Report
64.50.191.33
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 64.50.191.33 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.33.
Neighbors in 64.50.191.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 111 | Unknown | Low | Service on port 111 |
| CVE ID | Link |
|---|---|
| CVE-2017-8923 | NVD → |
| CVE-2007-3205 | NVD → |
| CVE-2024-3566 | NVD → |
| CVE-2020-7061 | NVD → |
| CVE-2020-7063 | NVD → |
| CVE-2019-11048 | NVD → |
| CVE-2022-31628 | NVD → |
| CVE-2019-11047 | NVD → |
| CVE-2019-11045 | NVD → |
| CVE-2019-11044 | NVD → |
| CVE-2020-7060 | NVD → |
| CVE-2022-31629 | NVD → |
| CVE-2020-7069 | NVD → |
| CVE-2019-11050 | NVD → |
| CVE-2020-7068 | NVD → |
| CVE-2020-7066 | NVD → |
| CVE-2020-7067 | NVD → |
| CVE-2013-2220 | NVD → |
| CVE-2024-25117 | NVD → |
| CVE-2020-7059 | NVD → |
| CVE-2020-7070 | NVD → |
| CVE-2020-7064 | NVD → |
| CVE-2022-37454 | NVD → |
| CVE-2020-7062 | NVD → |
| CVE-2022-4900 | NVD → |
🔴 Security scanning identified 26 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
64.50.191.33 has been assigned a threat score of 95/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
📊 Threat Analysis
Threat intelligence analysis has linked 64.50.191.33 to malicious activity originating from Los Angeles, United States, operating on the network of BreezeHost. The address has been under observation since its initial detection. The address has been active for 3 days in our monitoring system, producing 7 flagged requests at a rate of ~2.3/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. With a threat score of 95/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Related Threats
🏢 Same network: AS400810
64.50.191.32 (130)95.169.173.40 (130)151.243.143.47 (95)154.58.229.82 (95)95.169.173.32 (95)View all →Security Intelligence
💡 Directory Traversal Attacks
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.
💡 IPv6 Scanning Challenges
The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.