IP Threat Report
4.223.104.110
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 68 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 62 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 68 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 16 | Medium-risk: admin panels, config files | +60 | |
| Burst: 24 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 24 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Burst: 16 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 20 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 107 | Medium-risk: admin panels, config files | +60 | |
| Burst: 39 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 108 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 40 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 102 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 21 | Medium-risk: admin panels, config files | +60 | |
| Burst: 32 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 32 | Medium-risk: admin panels, config files | +60 | |
| Burst: 43 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 43 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 21 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 21 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 9 | Medium-risk: admin panels, config files | +60 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 12 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 19 | Medium-risk: admin panels, config files | +60 | |
| Burst: 19 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 19 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 30 | Medium-risk: admin panels, config files | +60 | |
| Burst: 30 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 30 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Burst: 9 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 10 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 152 | Medium-risk: admin panels, config files | +60 | |
| Burst: 47 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 141 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 56 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 167 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 53 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 146 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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 4.223.104.110 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 User-Agent Anomaly Defense
IP 4.223.104.110 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Path Enumeration Protection
Block scanning from 4.223.104.110: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 4.223.104.110.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 5432 | PostgreSQL | High | PostgreSQL database — direct database access risk |
⚠️ Network scanning reveals 1 dangerous service exposed on 4.223.104.110. These services should not be publicly accessible without strict firewall rules.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
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
4.223.104.110 has been assigned a threat score of 280/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 4.223.104.110, located in Gävle, Sweden, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. Our sensors captured 47 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~23.5 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. With 102 flagged addresses, Sweden represents a significant presence in our threat database. A score of 280/100 places this address in the top tier of severity. Block and investigate any historical connections.
This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
Related Threats
Security Intelligence
💡 User-Agent Analysis Techniques
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
💡 Submarine Cable and Internet Exchange Points
Internet traffic routing through a limited number of submarine cables and exchange points creates natural chokepoints. Understanding these routing patterns helps explain geographic clustering of certain attack types and latency-based scanning behaviors.