IP威胁报告
190.61.112.143
ABUSE.MOM — 规矩点，否则你将被曝光
地理位置与分类
检测签名
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| 404 ratio >= 60% | 大多数请求返回404——目录枚举 | +25 | |
| Danger strong hits: 1 | 高风险路径：Webshell、RCE、漏洞利用 | +25 | |
| Foreign referer | 来自无关外部域名的Referer | +10 |
观察到的活动
从服务器访问日志重建的HTTP请求。出于安全考虑，目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
时间线
网络供应商
建议
已采取和建议的措施
- IP 190.61.112.143 已在应用层封锁（HTTP 403）
- 建议在防火墙层（iptables/CSF）进行封锁
- 通过abuse联系方式向网络供应商举报
- 确保敏感文件（.env、.git、备份）无法从网络访问
🔎 目录扫描防御
IP 190.61.112.143正在枚举目录。在10次以上404错误后配置fail2ban apache-404 jail。禁用目录列表。
黑名单状态 (DNSBL)
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查：Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
Threat Analysis
190.61.112.143 has been assigned a threat score of 60/100 (High). 此分数表明高威胁严重性。该IP显示出明确的恶意行为模式，需要立即采取防御措施。
The following attack categories were identified:
📊 Threat Analysis
地址190.61.112.143来源于San Salvador, SV，运营在Ufinet El Salvador的网络中。它是通过对受监控端点的入站网络流量进行自动分析而被识别的。 我们的传感器在1天内捕获了来自此地址的163次恶意请求，反映出每天约163次的持续攻击节奏。 此IP被识别为VPN或代理端点，通常用于掩盖攻击流量的真实来源并绕过地理或信誉封锁。 该IP表现出目录枚举行为，系统地请求不存在的路径以发现隐藏文件和配置错误的资源。 评分60/100需要主动监控和速率限制。建议对敏感系统进行完全封锁。
This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.
Related Threats
🇸🇻 Top threats from SV
201.247.171.155 (103)190.57.98.220 (68)190.57.102.251 (68)190.57.100.154 (68)181.119.99.187 (60)View all →🏢 Same network: AS52468
View all →Security Intelligence
💡 API Abuse and Enumeration
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.
💡 Patch Management Urgency
The window between vulnerability disclosure and exploitation continues to shrink. Critical CVEs are now exploited within hours of publication. Automated patch management, virtual patching through WAFs, and rapid deployment pipelines are essential for timely remediation.