
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 112.50.180.206 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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.
112.50.180.206 has been assigned a threat score of 85/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
Our monitoring infrastructure has identified 112.50.180.206, geolocated to Guangzhou, China, operating on the network of China Mobile, as a source of suspicious network activity. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 166 flagged addresses, China represents a significant presence in our threat database. At 85/100, this IP warrants immediate defensive action.
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.
Content Security Policy headers instruct browsers to restrict resource loading, mitigating XSS and data injection attacks. Properly configured CSP policies prevent inline script execution, restrict iframe embedding, and control which domains can serve content.