
ABUSE.MOM — 规矩点,否则你将被曝光
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| Danger strong hits: 1 | 高风险路径:Webshell、RCE、漏洞利用 | +25 | |
| Danger medium hits: 1 | 中等风险:管理面板、配置文件 | +10 | |
| 404 ratio >= 60% | 大多数请求返回404——目录枚举 | +25 | |
| POST requests present | 自动分析检测到行为异常 | +8 |
从服务器访问日志重建的HTTP请求。出于安全考虑,目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 185.33.45.42正在枚举目录。在10次以上404错误后配置fail2ban apache-404 jail。禁用目录列表。
来自Shodan的网络侦察数据。开放端口可能表示正在运行的服务、错误配置或潜在的攻击面。
| Port | Service | Risk | Description |
|---|---|---|---|
| 21 | FTP | Medium | File Transfer Protocol — often targeted for anonymous login attacks |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 161 | Unknown | Low | Service on port 161 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 1701 | Unknown | Low | Service on port 1701 |
| 1723 | PPTP | Low | Service on port 1723 |
| 2000 | Unknown | Low | Service on port 2000 |
| 8291 | MikroTik | High | MikroTik Winbox — router management, targeted by VPNFilter malware |
⚠️ 在185.33.45.42上检测到2个高风险端口。 这些服务在没有严格防火墙规则的情况下不应公开访问。
数据来源:Shodan InternetDB。独立于abuse.mom进行扫描。
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查:Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
185.33.45.42 has been assigned a threat score of 68/100 (High). 这将其归类为高严重性威胁。建议对敏感基础设施进行主动封锁。
The following attack categories were identified:
威胁情报分析将185.33.45.42与来自Baghdad, IQ,运营在Smart Technology for Communications Services LLC的网络中的恶意活动相关联。该地址自首次检测以来一直处于观察状态。 我们的传感器在1天内捕获了来自此地址的2次恶意请求,反映出每天约2次的持续攻击节奏。 这是一个住宅IP地址,表明可能是被入侵的家用设备,如路由器、智能设备或参与僵尸网络的受感染工作站。 该IP表现出目录枚举行为,系统地请求不存在的路径以发现隐藏文件和配置错误的资源。 IQ目前在我们的数据库中占115个被封锁IP,使其成为恶意流量的重要来源。 评分68/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.
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.
Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.