IP威胁报告
165.22.240.105
ABUSE.MOM — 规矩点，否则你将被曝光
地理位置与分类
检测签名
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| UA changed for same IP | 多个User-Agent——机器人轮换技术 | +25 | |
| Danger strong hits: 4 | 高风险路径：Webshell、RCE、漏洞利用 | +100 | |
| Danger medium hits: 3 | 中等风险：管理面板、配置文件 | +30 | |
| 404 ratio >= 60% | 大多数请求返回404——目录枚举 | +25 | |
| Probe pattern 302->404 same path | 自动分析检测到行为异常 | +20 | |
| Foreign referer seen | 来自无关外部域名的Referer | +10 | |
| Danger strong hits: 6 | 高风险路径：Webshell、RCE、漏洞利用 | +100 | |
| 404 ratio 40-60% | 大多数请求返回404——目录枚举 | +15 | |
| Burst: 6 req / 2s | 请求频率异常——自动扫描 | +35 |
观察到的活动
从服务器访问日志重建的HTTP请求。出于安全考虑，目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
时间线
网络供应商
建议
已采取和建议的措施
- IP 165.22.240.105 已在应用层封锁（HTTP 403）
- 建议在防火墙层（iptables/CSF）进行封锁
- 通过abuse联系方式向网络供应商举报
- 确保敏感文件（.env、.git、备份）无法从网络访问
🤖 User-Agent异常防御
IP 165.22.240.105显示可疑的UA行为。阻止空User-Agent请求。为敏感端点实施基于JavaScript的机器人检测。
🔎 目录扫描防御
IP 165.22.240.105正在枚举目录。在10次以上404错误后配置fail2ban apache-404 jail。禁用目录列表。
🌊 洪水/DDoS缓解
在nginx中实施limit_req_zone。部署具有DDoS防护的CDN。配置SYN cookies和连接跟踪以限制165.22.240.105。
开放端口和服务
来自Shodan的网络侦察数据。开放端口可能表示正在运行的服务、错误配置或潜在的攻击面。
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 10001 | Unknown | Low | Service on port 10001 |
| 10002 | Unknown | Low | Service on port 10002 |
| 10003 | Unknown | Low | Service on port 10003 |
| 10008 | Unknown | Low | Service on port 10008 |
| 10014 | Unknown | Low | Service on port 10014 |
| 10249 | Unknown | Low | Service on port 10249 |
| 10250 | Unknown | Low | Service on port 10250 |
| 10348 | Unknown | Low | Service on port 10348 |
| 11211 | Unknown | Low | Service on port 11211 |
| 12000 | Unknown | Low | Service on port 12000 |
| 12016 | Unknown | Low | Service on port 12016 |
| 12124 | Unknown | Low | Service on port 12124 |
| 12159 | Unknown | Low | Service on port 12159 |
| 12192 | Unknown | Low | Service on port 12192 |
| 12251 | Unknown | Low | Service on port 12251 |
| 12260 | Unknown | Low | Service on port 12260 |
| 12334 | Unknown | Low | Service on port 12334 |
| 12337 | Unknown | Low | Service on port 12337 |
| 12354 | Unknown | Low | Service on port 12354 |
| 12397 | Unknown | Low | Service on port 12397 |
| 12410 | Unknown | Low | Service on port 12410 |
| 12465 | Unknown | Low | Service on port 12465 |
| 12466 | Unknown | Low | Service on port 12466 |
| 12503 | Unknown | Low | Service on port 12503 |
| 12535 | Unknown | Low | Service on port 12535 |
| 12547 | Unknown | Low | Service on port 12547 |
| 12557 | Unknown | Low | Service on port 12557 |
| 12571 | Unknown | Low | Service on port 12571 |
| 13084 | Unknown | Low | Service on port 13084 |
| 13579 | Unknown | Low | Service on port 13579 |
| 13718 | Unknown | Low | Service on port 13718 |
| 14875 | Unknown | Low | Service on port 14875 |
| 14903 | Unknown | Low | Service on port 14903 |
| 15123 | Unknown | Low | Service on port 15123 |
| 16010 | Unknown | Low | Service on port 16010 |
| 16080 | Unknown | Low | Service on port 16080 |
| 16093 | Unknown | Low | Service on port 16093 |
| 16401 | Unknown | Low | Service on port 16401 |
| 16993 | Unknown | Low | Service on port 16993 |
| 17082 | Unknown | Low | Service on port 17082 |
| 18003 | Unknown | Low | Service on port 18003 |
| 18036 | Unknown | Low | Service on port 18036 |
| 18047 | Unknown | Low | Service on port 18047 |
| 18051 | Unknown | Low | Service on port 18051 |
| 18053 | Unknown | Low | Service on port 18053 |
| 18061 | Unknown | Low | Service on port 18061 |
| 18068 | Unknown | Low | Service on port 18068 |
| 18072 | Unknown | Low | Service on port 18072 |
| 19071 | Unknown | Low | Service on port 19071 |
| 19080 | Unknown | Low | Service on port 19080 |
| 19527 | Unknown | Low | Service on port 19527 |
| 30011 | Unknown | Low | Service on port 30011 |
| 30473 | Unknown | Low | Service on port 30473 |
| 30479 | Unknown | Low | Service on port 30479 |
| 31337 | Unknown | Low | Service on port 31337 |
| 31380 | Unknown | Low | Service on port 31380 |
| 33060 | Unknown | Low | Service on port 33060 |
| 33700 | Unknown | Low | Service on port 33700 |
| 35554 | Unknown | Low | Service on port 35554 |
| 35874 | Unknown | Low | Service on port 35874 |
| 37777 | Unknown | Low | Service on port 37777 |
| 38779 | Unknown | Low | Service on port 38779 |
数据来源：Shodan InternetDB。独立于abuse.mom进行扫描。
黑名单状态 (DNSBL)
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查：Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
Threat Analysis
165.22.240.105 has been assigned a threat score of 215/100 (Critical). 这将其归入严重威胁类别。强烈建议在所有网络边界立即进行封锁。
The following attack categories were identified:
📊 Threat Analysis
威胁情报分析将165.22.240.105与来自Singapore, Singapore，运营在DigitalOcean, LLC的网络中的恶意活动相关联。该地址自首次检测以来一直处于观察状态。 我们的传感器在1天内捕获了来自此地址的2次恶意请求，反映出每天约2次的持续攻击节奏。 该IP被归类为托管/数据中心基础设施，通常与用于自动化攻击活动、僵尸网络命令控制或大规模漏洞扫描的租用服务器相关联。 3种不同攻击向量的组合表明这是一个复杂的多方位威胁行为者，部署自动化工具同时探测多个攻击面。 我们的记录显示来自Singapore的41个恶意IP，使其成为全球威胁活动的值得注意的贡献者。 威胁评分215/100，此IP属于我们数据库中最危险的地址之一。强烈建议立即完全封锁。
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.
Related Threats
Security Intelligence
💡 User-Agent Analysis Techniques
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
💡 Subnet-Level vs IP-Level Blocking
When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.