
ABUSE.MOM — 规矩点,否则你将被曝光
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| UA changed for same IP | 多个User-Agent——机器人轮换技术 | +25 | |
| Foreign referer seen | 来自无关外部域名的Referer | +10 | |
| Burst: 8 req / 2s | 请求频率异常——自动扫描 | +35 | |
| Burst: 10 req / 10s | 请求频率异常——自动扫描 | +35 | |
| Danger strong hits: 1 | 高风险路径:Webshell、RCE、漏洞利用 | +25 | |
| 404 ratio >= 60% | 大多数请求返回404——目录枚举 | +25 |
从服务器访问日志重建的HTTP请求。出于安全考虑,目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 138.199.143.30显示可疑的UA行为。阻止空User-Agent请求。为敏感端点实施基于JavaScript的机器人检测。
在nginx中实施limit_req_zone。部署具有DDoS防护的CDN。配置SYN cookies和连接跟踪以限制138.199.143.30。
IP 138.199.143.30正在枚举目录。在10次以上404错误后配置fail2ban apache-404 jail。禁用目录列表。
来自Shodan的网络侦察数据。开放端口可能表示正在运行的服务、错误配置或潜在的攻击面。
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8443 | HTTPS-Alt | Low | Service on port 8443 |
| 9090 | Unknown | Low | Service on port 9090 |
| 9100 | Unknown | Low | Service on port 9100 |
| 9353 | Unknown | Low | Service on port 9353 |
| 10000 | Unknown | Low | Service on port 10000 |
| 10250 | Unknown | Low | Service on port 10250 |
数据来源:Shodan InternetDB。独立于abuse.mom进行扫描。
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查:Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
138.199.143.30 has been assigned a threat score of 105/100 (Critical). 这是一个严重级别的威胁。系统管理员应将此IP视为敌对地址,无例外地阻止所有入站连接。
The following attack categories were identified:
IP地址138.199.143.30已追溯至Falkenstein, Germany,运营在Hetzner Online GmbH的网络中。我们的威胁检测系统根据观察到的恶意行为模式标记了此地址。 我们的传感器在36天内捕获了来自此地址的3次恶意请求,反映出每天约0.1次的持续攻击节奏。 该IP从数据中心基础设施运营,是有组织攻击行动中使用的典型地址。 3种不同攻击向量的组合表明这是一个复杂的多方位威胁行为者,部署自动化工具同时探测多个攻击面。 我们的记录显示来自Germany的163个恶意IP,使其成为全球威胁活动的重要贡献者。 评分105/100将此地址置于最高严重性级别。应封锁并调查任何历史连接。
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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
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.