
ABUSE.MOM — 规矩点,否则你将被曝光
| 签名 | 描述 | 分数 | 严重性 |
|---|---|---|---|
| Danger medium hits: 8 | 中等风险:管理面板、配置文件 | +60 | |
| Foreign referer seen | 来自无关外部域名的Referer | +10 |
从服务器访问日志重建的HTTP请求。出于安全考虑,目标域名已隐藏。
* Typical request patterns for detected signatures. Actual target domains are redacted.
将58.216.109.17添加到防火墙封锁列表。检查日志中的成功连接。在所有面向公众的服务上启用全面日志记录。
来自同一/24子网的其他被封锁IP——表明该网络范围存在系统性滥用。
来自Shodan的网络侦察数据。开放端口可能表示正在运行的服务、错误配置或潜在的攻击面。
| Port | Service | Risk | Description |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 161 | Unknown | Low | Service on port 161 |
| 800 | Unknown | Low | Service on port 800 |
| 843 | Unknown | Low | Service on port 843 |
| 902 | Unknown | Low | Service on port 902 |
| 5600 | Unknown | Low | Service on port 5600 |
| 8001 | Unknown | Low | Service on port 8001 |
| 8043 | Unknown | Low | Service on port 8043 |
| 8068 | Unknown | Low | Service on port 8068 |
| 8069 | Unknown | Low | Service on port 8069 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8081 | Unknown | Low | Service on port 8081 |
| 8089 | Unknown | Low | Service on port 8089 |
| 8099 | Unknown | Low | Service on port 8099 |
| 8443 | HTTPS-Alt | Low | Service on port 8443 |
| 9101 | Unknown | Low | Service on port 9101 |
数据来源:Shodan InternetDB。独立于abuse.mom进行扫描。
该IP已通过全球邮件服务器和防火墙使用的主要DNS黑名单进行检查。
已检查:Spamhaus、SpamCop、Barracuda、SORBS、CBL、UCEProtect。
58.216.109.17 has been assigned a threat score of 70/100 (High). 此分数表明高威胁严重性。该IP显示出明确的恶意行为模式,需要立即采取防御措施。
58.216.109.17注册在Nanjing, China,运营在China Telecom的网络中。该IP在触发多个行为检测签名后首次出现在我们的威胁源中。 在其34天的观察窗口期间,我们记录了来自此IP的2次敌对请求——平均每天约0.1次。 这是一个住宅IP地址,表明可能是被入侵的家用设备,如路由器、智能设备或参与僵尸网络的受感染工作站。 我们的记录显示来自China的105个恶意IP,使其成为全球威胁活动的重要贡献者。 威胁评分70/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.
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.