
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: spider | Known bot/crawler User-Agent detected | +40 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Address UA spoofing from 223.109.252.184: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
IP 223.109.252.184 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.
223.109.252.184 has been assigned a threat score of 75/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.
The following attack categories were identified:
Our monitoring infrastructure has identified 223.109.252.184, geolocated to Nanjing, China, operating on the network of China Mobile communications corporation, as a source of suspicious network activity. During its 16-day observation window, we recorded 3 hostile requests from this IP — roughly 0.2 per day on average. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. China currently accounts for 201 blocked IPs in our database, making it a significant source of malicious traffic. At 75/100, this IP warrants immediate defensive action.
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.
Attacks targeting software supply chains compromise trusted update mechanisms to distribute malware at scale. Dependency confusion, typosquatting in package registries, and compromised build pipelines threaten even organizations with strong direct security postures.