IP威胁报告
14.224.170.240
ABUSE.MOM — 规矩点，否则你将被曝光
地理位置与分类
检测签名
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| Danger medium hits: 8 | 中等风险：管理面板、配置文件 | +60 | |
| 404 ratio 40-60% | 大多数请求返回404——目录枚举 | +15 | |
| Probe pattern 302->404 same path | 自动分析检测到行为异常 | +20 | |
| Foreign referer seen | 来自无关外部域名的Referer | +10 | |
| Danger medium hits: 6 | 中等风险：管理面板、配置文件 | +60 |
观察到的活动
从服务器访问日志重建的HTTP请求。出于安全考虑，目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
时间线
网络供应商
建议
已采取和建议的措施
- IP 14.224.170.240 已在应用层封锁（HTTP 403）
- 建议在防火墙层（iptables/CSF）进行封锁
- 通过abuse联系方式向网络供应商举报
- 确保敏感文件（.env、.git、备份）无法从网络访问
🔎 目录扫描防御
IP 14.224.170.240正在枚举目录。在10次以上404错误后配置fail2ban apache-404 jail。禁用目录列表。
开放端口和服务
来自Shodan的网络侦察数据。开放端口可能表示正在运行的服务、错误配置或潜在的攻击面。
| Port | Service | Risk | Description |
|---|---|---|---|
| 2000 | Unknown | Low | Service on port 2000 |
| 18000 | Unknown | Low | Service on port 18000 |
| 18002 | Unknown | Low | Service on port 18002 |
| 18003 | Unknown | Low | Service on port 18003 |
| 18004 | Unknown | Low | Service on port 18004 |
| 18005 | Unknown | Low | Service on port 18005 |
| 18006 | Unknown | Low | Service on port 18006 |
| 18009 | Unknown | Low | Service on port 18009 |
| 18010 | Unknown | Low | Service on port 18010 |
| 18011 | Unknown | Low | Service on port 18011 |
| 18012 | Unknown | Low | Service on port 18012 |
| 18014 | Unknown | Low | Service on port 18014 |
| 18015 | Unknown | Low | Service on port 18015 |
| 18016 | Unknown | Low | Service on port 18016 |
| 18018 | Unknown | Low | Service on port 18018 |
| 18019 | Unknown | Low | Service on port 18019 |
| 18020 | Unknown | Low | Service on port 18020 |
| 18021 | Unknown | Low | Service on port 18021 |
| 18023 | Unknown | Low | Service on port 18023 |
| 18024 | Unknown | Low | Service on port 18024 |
| 18025 | Unknown | Low | Service on port 18025 |
| 18027 | Unknown | Low | Service on port 18027 |
| 18028 | Unknown | Low | Service on port 18028 |
| 18031 | Unknown | Low | Service on port 18031 |
| 18033 | Unknown | Low | Service on port 18033 |
| 18035 | Unknown | Low | Service on port 18035 |
| 18042 | Unknown | Low | Service on port 18042 |
| 18047 | Unknown | Low | Service on port 18047 |
| 18048 | Unknown | Low | Service on port 18048 |
| 18053 | Unknown | Low | Service on port 18053 |
| 18055 | Unknown | Low | Service on port 18055 |
| 18056 | Unknown | Low | Service on port 18056 |
| 18057 | Unknown | Low | Service on port 18057 |
| 18058 | Unknown | Low | Service on port 18058 |
| 18059 | Unknown | Low | Service on port 18059 |
| 18060 | Unknown | Low | Service on port 18060 |
| 18061 | Unknown | Low | Service on port 18061 |
| 18063 | Unknown | Low | Service on port 18063 |
| 18064 | Unknown | Low | Service on port 18064 |
| 18065 | Unknown | Low | Service on port 18065 |
| 18068 | Unknown | Low | Service on port 18068 |
| 18069 | Unknown | Low | Service on port 18069 |
| 18070 | Unknown | Low | Service on port 18070 |
| 18071 | Unknown | Low | Service on port 18071 |
| 18073 | Unknown | Low | Service on port 18073 |
| 18074 | Unknown | Low | Service on port 18074 |
| 18077 | Unknown | Low | Service on port 18077 |
| 18078 | Unknown | Low | Service on port 18078 |
| 18081 | Unknown | Low | Service on port 18081 |
| 18084 | Unknown | Low | Service on port 18084 |
| 18086 | Unknown | Low | Service on port 18086 |
| 18087 | Unknown | Low | Service on port 18087 |
| 18090 | Unknown | Low | Service on port 18090 |
| 18091 | Unknown | Low | Service on port 18091 |
| 18093 | Unknown | Low | Service on port 18093 |
| 18094 | Unknown | Low | Service on port 18094 |
| 18095 | Unknown | Low | Service on port 18095 |
| 18096 | Unknown | Low | Service on port 18096 |
| 18097 | Unknown | Low | Service on port 18097 |
| 18098 | Unknown | Low | Service on port 18098 |
| 18100 | Unknown | Low | Service on port 18100 |
| 18101 | Unknown | Low | Service on port 18101 |
| 18102 | Unknown | Low | Service on port 18102 |
| 18103 | Unknown | Low | Service on port 18103 |
| 18105 | Unknown | Low | Service on port 18105 |
| 18107 | Unknown | Low | Service on port 18107 |
| 18110 | Unknown | Low | Service on port 18110 |
| 18111 | Unknown | Low | Service on port 18111 |
| 18113 | Unknown | Low | Service on port 18113 |
| 18182 | Unknown | Low | Service on port 18182 |
| 18200 | Unknown | Low | Service on port 18200 |
| 18225 | Unknown | Low | Service on port 18225 |
| 18239 | Unknown | Low | Service on port 18239 |
| 18245 | Unknown | Low | Service on port 18245 |
| 18264 | Unknown | Low | Service on port 18264 |
| 18368 | Unknown | Low | Service on port 18368 |
| 18443 | Unknown | Low | Service on port 18443 |
| 18556 | Unknown | Low | Service on port 18556 |
| 18765 | Unknown | Low | Service on port 18765 |
| 18789 | Unknown | Low | Service on port 18789 |
| 18888 | Unknown | Low | Service on port 18888 |
| CVE ID | Link |
|---|---|
| CVE-2025-62168 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2024-45802 | NVD → |
🔴 此主机有4个已知CVE与其暴露的服务相关联。多个漏洞表明补丁管理存在漏洞。 请在NVD数据库中查看每个CVE的详细信息。
数据来源：Shodan InternetDB。独立于abuse.mom进行扫描。
黑名单状态 (DNSBL)
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查：Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
Threat Analysis
14.224.170.240 has been assigned a threat score of 105/100 (Critical). 这是一个严重级别的威胁。系统管理员应将此IP视为敌对地址，无例外地阻止所有入站连接。
The following attack categories were identified:
📊 Threat Analysis
我们的监控基础设施已将14.224.170.240（地理位置为Ho Chi Minh City, Vietnam，运营在VNPT的网络中）识别为可疑网络活动的来源。 在24天的时间内，此IP产生了2次恶意请求，平均每天约0.1次请求。 该地址被归类为住宅，意味着它可能属于终端用户ISP连接。来自住宅IP的恶意活动通常表明设备已被入侵或属于僵尸网络。 该IP表现出目录枚举行为，系统地请求不存在的路径以发现隐藏文件和配置错误的资源。 Vietnam目前在我们的数据库中占196个被封锁IP，使其成为恶意流量的重要来源。 评分105/100将此地址置于最高严重性级别。应封锁并调查任何历史连接。
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
Security Intelligence
💡 Server-Side Request Forgery (SSRF)
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.
💡 Bulletproof Hosting Ecosystem
Bulletproof hosting providers deliberately ignore abuse complaints, creating safe havens for malicious operations. These providers often operate in jurisdictions with weak cybercrime enforcement, offering services specifically marketed to criminal organizations.