
ABUSE.MOM — 规矩点,否则你将被曝光
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| Danger medium hits: 6 | 中等风险:管理面板、配置文件 | +60 | |
| 404 ratio 40-60% | 大多数请求返回404——目录枚举 | +15 | |
| Foreign referer seen | 来自无关外部域名的Referer | +10 |
从服务器访问日志重建的HTTP请求。出于安全考虑,目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 38.34.179.46正在枚举目录。在10次以上404错误后配置fail2ban apache-404 jail。禁用目录列表。
来自同一/24子网的其他被封锁IP——表明该网络范围存在系统性滥用。
来自Shodan的网络侦察数据。开放端口可能表示正在运行的服务、错误配置或潜在的攻击面。
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 8447 | Unknown | Low | Service on port 8447 |
| 8449 | Unknown | Low | Service on port 8449 |
| 8451 | Unknown | Low | Service on port 8451 |
| 8452 | Unknown | Low | Service on port 8452 |
| 8453 | Unknown | Low | Service on port 8453 |
| 9100 | Unknown | Low | Service on port 9100 |
| 10250 | Unknown | Low | Service on port 10250 |
数据来源:Shodan InternetDB。独立于abuse.mom进行扫描。
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查:Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
38.34.179.46 has been assigned a threat score of 85/100 (Critical). 凭借此评分,该IP属于严重威胁级别——是我们监控数据库中最危险的地址之一。
The following attack categories were identified:
威胁情报分析将38.34.179.46与来自Redondo Beach, United States,运营在Enzu Inc的网络中的恶意活动相关联。该地址自首次检测以来一直处于观察状态。 我们的传感器在1天内捕获了来自此地址的1次恶意请求,反映出每天约1次的持续攻击节奏。 从住宅网络运营,此IP可能代表一个被入侵的家庭网关或已被招募到更大攻击基础设施中的IoT设备。 该IP表现出目录枚举行为,系统地请求不存在的路径以发现隐藏文件和配置错误的资源。 United States目前在我们的数据库中占173个被封锁IP,使其成为恶意流量的重要来源。 威胁评分85/100将此IP置于高风险类别。建议在防火墙级别进行封锁。
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.
Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.
SSH servers face constant brute force attacks targeting common usernames and weak passwords. Key-based authentication, fail2ban, non-standard ports, and IP allowlisting dramatically reduce the attack surface. Monitoring auth logs reveals active campaigns and compromised credentials.