
ABUSE.MOM — 规矩点,否则你将被曝光
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| UA changed for same IP | 多个User-Agent——机器人轮换技术 | +25 | |
| Danger strong hits: 3 | 高风险路径:Webshell、RCE、漏洞利用 | +75 | |
| Danger medium hits: 1 | 中等风险:管理面板、配置文件 | +10 | |
| Foreign referer seen | 来自无关外部域名的Referer | +10 |
从服务器访问日志重建的HTTP请求。出于安全考虑,目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 193.37.133.12显示可疑的UA行为。阻止空User-Agent请求。为敏感端点实施基于JavaScript的机器人检测。
来自Shodan的网络侦察数据。开放端口可能表示正在运行的服务、错误配置或潜在的攻击面。
| Port | Service | Risk | Description |
|---|---|---|---|
| 3389 | RDP | High | Remote Desktop Protocol — primary target for ransomware attacks |
| 5432 | PostgreSQL | High | PostgreSQL database — direct database access risk |
| 5433 | Unknown | Low | Service on port 5433 |
| 6000 | Unknown | Low | Service on port 6000 |
| 6002 | Unknown | Low | Service on port 6002 |
| 6003 | Unknown | Low | Service on port 6003 |
| 6348 | Unknown | Low | Service on port 6348 |
| 6352 | Unknown | Low | Service on port 6352 |
| 6363 | Unknown | Low | Service on port 6363 |
| 6379 | Redis | Critical | Redis in-memory database — frequently misconfigured without auth |
| 6380 | Unknown | Low | Service on port 6380 |
| 6400 | Unknown | Low | Service on port 6400 |
| 6405 | Unknown | Low | Service on port 6405 |
| 6432 | Unknown | Low | Service on port 6432 |
| 6433 | Unknown | Low | Service on port 6433 |
| 6440 | Unknown | Low | Service on port 6440 |
| 6443 | Unknown | Low | Service on port 6443 |
| 6887 | Unknown | Low | Service on port 6887 |
| 6955 | Unknown | Low | Service on port 6955 |
| 6998 | Unknown | Low | Service on port 6998 |
| 7001 | Unknown | Low | Service on port 7001 |
| 7002 | Unknown | Low | Service on port 7002 |
| 7003 | Unknown | Low | Service on port 7003 |
| 7005 | Unknown | Low | Service on port 7005 |
| 7007 | Unknown | Low | Service on port 7007 |
| 7010 | Unknown | Low | Service on port 7010 |
| 7012 | Unknown | Low | Service on port 7012 |
| 7013 | Unknown | Low | Service on port 7013 |
| 7014 | Unknown | Low | Service on port 7014 |
| 7016 | Unknown | Low | Service on port 7016 |
| 7020 | Unknown | Low | Service on port 7020 |
| 7022 | Unknown | Low | Service on port 7022 |
| 7057 | Unknown | Low | Service on port 7057 |
| 7070 | Unknown | Low | Service on port 7070 |
| 7071 | Unknown | Low | Service on port 7071 |
| 7078 | Unknown | Low | Service on port 7078 |
| 7079 | Unknown | Low | Service on port 7079 |
| 7080 | Unknown | Low | Service on port 7080 |
| 7082 | Unknown | Low | Service on port 7082 |
| 7083 | Unknown | Low | Service on port 7083 |
| 7085 | Unknown | Low | Service on port 7085 |
| 7086 | Unknown | Low | Service on port 7086 |
| 7087 | Unknown | Low | Service on port 7087 |
| 7088 | Unknown | Low | Service on port 7088 |
| 7090 | Unknown | Low | Service on port 7090 |
| 7100 | Unknown | Low | Service on port 7100 |
| 7102 | Unknown | Low | Service on port 7102 |
| 7105 | Unknown | Low | Service on port 7105 |
| 7171 | Unknown | Low | Service on port 7171 |
| 7172 | Unknown | Low | Service on port 7172 |
| 7173 | Unknown | Low | Service on port 7173 |
| 7218 | Unknown | Low | Service on port 7218 |
| 8502 | Unknown | Low | Service on port 8502 |
| 9001 | Unknown | Low | Service on port 9001 |
⚠️ 在193.37.133.12上检测到3个高风险端口。暴露的RDP (3389)是勒索软件攻击的首要入口。 开放的数据库端口表明可能存在数据泄露风险。 这些服务在没有严格防火墙规则的情况下不应公开访问。
数据来源:Shodan InternetDB。独立于abuse.mom进行扫描。
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查:Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
193.37.133.12 has been assigned a threat score of 120/100 (Critical). 这是一个严重级别的威胁。系统管理员应将此IP视为敌对地址,无例外地阻止所有入站连接。
The following attack categories were identified:
IP地址193.37.133.12已追溯至New York Mills, United States,运营在PureVoltage Hosting Inc.的网络中。我们的威胁检测系统根据观察到的恶意行为模式标记了此地址。 在1天的时间内,此IP产生了1次恶意请求,平均每天约1次请求。 该IP从数据中心基础设施运营,是有组织攻击行动中使用的典型地址。 检测到可疑的User-Agent异常,包括空的、伪造的或快速轮换的UA字符串——自动化扫描工具的特征。 我们的记录显示来自United States的198个恶意IP,使其成为全球威胁活动的重要贡献者。 评分120/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.
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.