IP威胁报告
80.71.141.185
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 80.71.141.185 已在应用层封锁（HTTP 403）
- 建议在防火墙层（iptables/CSF）进行封锁
- 通过abuse联系方式向网络供应商举报
- 确保敏感文件（.env、.git、备份）无法从网络访问
🔎 目录扫描防御
IP 80.71.141.185正在枚举目录。在10次以上404错误后配置fail2ban apache-404 jail。禁用目录列表。
黑名单状态 (DNSBL)
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查：Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
Threat Analysis
80.71.141.185 has been assigned a threat score of 68/100 (High). 该IP被评为高级别威胁。网络管理员应实施阻止规则并监控来自此地址的任何连接。
The following attack categories were identified:
📊 Threat Analysis
我们的监控基础设施已将80.71.141.185（地理位置为Copenhagen, DK，运营在Parknet F.M.B.A.的网络中）识别为可疑网络活动的来源。 我们的传感器在1天内捕获了来自此地址的1次恶意请求，反映出每天约1次的持续攻击节奏。 该地址被归类为住宅，意味着它可能属于终端用户ISP连接。来自住宅IP的恶意活动通常表明设备已被入侵或属于僵尸网络。 该IP表现出目录枚举行为，系统地请求不存在的路径以发现隐藏文件和配置错误的资源。 DK目前在我们的数据库中占39个被封锁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.
Related Threats
🇩🇰 Top threats from DK
85.203.47.13 (295)85.203.47.213 (255)85.203.47.192 (255)85.203.47.6 (245)85.203.47.48 (235)View all →🏢 Same network: AS197301
View all →Security Intelligence
💡 Directory Traversal Attacks
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.
💡 GraphQL Security Risks
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.