IP Threat Report
223.109.255.169
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: spider | Known bot/crawler User-Agent detected | +40 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 223.109.255.169 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 223.109.255.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 Bot Detection
Address UA spoofing from 223.109.255.169: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Directory Scan Defense
IP 223.109.255.169 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Neighbors in 223.109.255.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
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.
Threat Analysis
223.109.255.169 has been assigned a threat score of 65/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 223.109.255.169, geolocated to Nanjing, China, operating on the network of China Mobile communications corporation, as a source of suspicious network activity. Over a period of 34 days, this IP generated 4 malicious requests, averaging approximately 0.1 requests per day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 201 flagged addresses, China represents a significant presence in our threat database. The score of 65/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
Related Threats
Security Intelligence
💡 HTTP Header Analysis for Threat Detection
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.
💡 HTTP/2 and HTTP/3 Security Implications
Modern HTTP protocols introduce new attack surfaces including stream multiplexing abuse, header compression attacks (HPACK bombing), and rapid reset attacks. Security tools must evolve to handle these protocol-specific threats effectively.