
ABUSE.MOM — 规矩点,否则你将被曝光
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| UA bot: Go-http-client | 检测到已知机器人/爬虫的User-Agent | +40 | |
| Danger strong hits: 10 | 高风险路径:Webshell、RCE、漏洞利用 | +100 | |
| 404 ratio 40-60% | 大多数请求返回404——目录枚举 | +15 | |
| Foreign referer seen | 来自无关外部域名的Referer | +10 |
从服务器访问日志重建的HTTP请求。出于安全考虑,目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 64.23.130.133显示可疑的UA行为。阻止空User-Agent请求。为敏感端点实施基于JavaScript的机器人检测。
IP 64.23.130.133正在枚举目录。在10次以上404错误后配置fail2ban apache-404 jail。禁用目录列表。
来自Shodan的网络侦察数据。开放端口可能表示正在运行的服务、错误配置或潜在的攻击面。
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 25 | SMTP | Medium | SMTP mail server — can be abused for spam relay |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8443 | HTTPS-Alt | Low | Service on port 8443 |
⚠️ 在64.23.130.133上检测到1个高风险端口。 这些服务在没有严格防火墙规则的情况下不应公开访问。
数据来源:Shodan InternetDB。独立于abuse.mom进行扫描。
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查:Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
64.23.130.133 has been assigned a threat score of 165/100 (Critical). 这是一个严重级别的威胁。系统管理员应将此IP视为敌对地址,无例外地阻止所有入站连接。
The following attack categories were identified:
IP地址64.23.130.133已追溯至Santa Clara, United States,运营在DigitalOcean, LLC的网络中。我们的威胁检测系统根据观察到的恶意行为模式标记了此地址。 在其1天的观察窗口期间,我们记录了来自此IP的1次敌对请求——平均每天约1次。 被归类为托管IP,此地址可能运行在租用的服务器或云实例上。攻击者偏好数据中心IP因其高带宽和一次性特点。 识别出两种攻击模式(User-Agent Anomaly和Path Enumeration),表明这是一个针对多个漏洞的半自动化攻击活动。 我们的记录显示来自United States的128个恶意IP,使其成为全球威胁活动的重要贡献者。 威胁评分165/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.
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.
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.