IP威胁报告
8.219.175.223
ABUSE.MOM — 规矩点，否则你将被曝光
地理位置与分类
检测签名
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| UA suspicious (short/empty) | 自动分析检测到行为异常 | +15 | |
| Danger strong hits: 2 | 高风险路径：Webshell、RCE、漏洞利用 | +50 | |
| 404 ratio 40-60% | 大多数请求返回404——目录枚举 | +15 | |
| Probe pattern 302->404 same path | 自动分析检测到行为异常 | +20 |
观察到的活动
从服务器访问日志重建的HTTP请求。出于安全考虑，目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
时间线
网络供应商
建议
已采取和建议的措施
- IP 8.219.175.223 已在应用层封锁（HTTP 403）
- 建议在防火墙层（iptables/CSF）进行封锁
- 在同一/24子网中检测到其他恶意IP——建议封锁 8.219.175.0/24
- 通过abuse联系方式向网络供应商举报
- 确保敏感文件（.env、.git、备份）无法从网络访问
🤖 User-Agent异常防御
IP 8.219.175.223显示可疑的UA行为。阻止空User-Agent请求。为敏感端点实施基于JavaScript的机器人检测。
🔎 目录扫描防御
IP 8.219.175.223正在枚举目录。在10次以上404错误后配置fail2ban apache-404 jail。禁用目录列表。
开放端口和服务
来自Shodan的网络侦察数据。开放端口可能表示正在运行的服务、错误配置或潜在的攻击面。
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 1013 | Unknown | Low | Service on port 1013 |
| 1023 | Unknown | Low | Service on port 1023 |
| 1080 | Unknown | Low | Service on port 1080 |
| 1153 | Unknown | Low | Service on port 1153 |
| 1200 | Unknown | Low | Service on port 1200 |
| 1224 | Unknown | Low | Service on port 1224 |
| 1244 | Unknown | Low | Service on port 1244 |
| 1249 | Unknown | Low | Service on port 1249 |
| 1291 | Unknown | Low | Service on port 1291 |
| 1344 | Unknown | Low | Service on port 1344 |
| 1370 | Unknown | Low | Service on port 1370 |
| 1443 | Unknown | Low | Service on port 1443 |
| 1471 | Unknown | Low | Service on port 1471 |
| 1557 | Unknown | Low | Service on port 1557 |
| 1577 | Unknown | Low | Service on port 1577 |
| 1599 | Unknown | Low | Service on port 1599 |
| 1723 | PPTP | Low | Service on port 1723 |
| 1741 | Unknown | Low | Service on port 1741 |
| 1800 | Unknown | Low | Service on port 1800 |
| 1911 | Unknown | Low | Service on port 1911 |
| 1925 | Unknown | Low | Service on port 1925 |
| 1950 | Unknown | Low | Service on port 1950 |
| 1952 | Unknown | Low | Service on port 1952 |
| 1962 | Unknown | Low | Service on port 1962 |
| 1967 | Unknown | Low | Service on port 1967 |
| 1970 | Unknown | Low | Service on port 1970 |
| 1981 | Unknown | Low | Service on port 1981 |
| CVE ID | Link |
|---|---|
| CVE-2017-15906 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2018-20685 | NVD → |
| CVE-2018-15473 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2019-6109 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2019-6110 | NVD → |
| CVE-2019-6111 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2018-15919 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2008-3844 | NVD → |
🔴 此主机有20个已知CVE与其暴露的服务相关联。如此大量的漏洞强烈表明软件严重过时。 请在NVD数据库中查看每个CVE的详细信息。
数据来源：Shodan InternetDB。独立于abuse.mom进行扫描。
黑名单状态 (DNSBL)
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查：Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
Threat Analysis
8.219.175.223 has been assigned a threat score of 100/100 (Critical). 这是一个严重级别的威胁。系统管理员应将此IP视为敌对地址，无例外地阻止所有入站连接。
The following attack categories were identified:
📊 Threat Analysis
IP地址8.219.175.223已追溯至Singapore, Singapore，运营在Alibaba (US) Technology Co., Ltd.的网络中。我们的威胁检测系统根据观察到的恶意行为模式标记了此地址。 我们的传感器在1天内捕获了来自此地址的2次恶意请求，反映出每天约2次的持续攻击节奏。 这是一个住宅IP地址，表明可能是被入侵的家用设备，如路由器、智能设备或参与僵尸网络的受感染工作站。 识别出两种攻击模式（User-Agent Anomaly和Path Enumeration），表明这是一个针对多个漏洞的半自动化攻击活动。 我们的记录显示来自Singapore的108个恶意IP，使其成为全球威胁活动的重要贡献者。 威胁评分100/100，此IP属于我们数据库中最危险的地址之一。强烈建议立即完全封锁。
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
🇸🇬 Top threats from Singapore
85.203.23.12 (340)85.203.23.31 (330)84.17.39.195 (325)192.166.246.30 (325)85.203.21.101 (320)View all →Security Intelligence
💡 TLS Fingerprinting (JA3/JA4)
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
💡 Server-Side Template Injection
SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.