
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Add 117.72.168.90 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
117.72.168.90 has been assigned a threat score of 70/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.
Threat intelligence analysis has linked 117.72.168.90 to malicious activity originating from Chaowai, China, operating on the network of JDCOM. The address has been under observation since its initial detection. Our sensors captured 158 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~26.3 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. China currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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.
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.
HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.