IP Threat Report
104.46.226.22
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: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 136 | Medium-risk: admin panels, config files | +60 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 38 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 142 | Medium-risk: admin panels, config files | +60 | |
| Burst: 40 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 54 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 149 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 131 | Medium-risk: admin panels, config files | +60 | |
| Burst: 41 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 68 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 350 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 51 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 233 | Medium-risk: admin panels, config files | +60 | |
| Burst: 13 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 46 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 14 | Medium-risk: admin panels, config files | +60 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 20 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 69 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 266 | Medium-risk: admin panels, config files | +60 | |
| Burst: 44 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 222 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 443 | Medium-risk: admin panels, config files | +60 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 43 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 153 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger strong hits: 20 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 82 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 71 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 125 | Medium-risk: admin panels, config files | +60 | |
| Burst: 45 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 78 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 280 | Medium-risk: admin panels, config files | +60 | |
| Burst: 47 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 151 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 310 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 46 | Medium-risk: admin panels, config files | +60 | |
| Burst: 42 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 64 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 307 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 11 | Medium-risk: admin panels, config files | +60 | |
| Burst: 16 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 48 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 224 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 156 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 291 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 65 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 152 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 235 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 196 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 399 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 26 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 44 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 72 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 158 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 442 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 444 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 190 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 383 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 227 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 60 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 44 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 87 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 341 | Medium-risk: admin panels, config files | +60 | |
| Burst: 39 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 26 | Medium-risk: admin panels, config files | +60 | |
| Burst: 35 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 197 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 339 | Medium-risk: admin panels, config files | +60 |
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 104.46.226.22 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
🤖 Bot Detection
Address UA spoofing from 104.46.226.22: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 104.46.226.22.
🔎 Path Enumeration Protection
Block scanning from 104.46.226.22: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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
104.46.226.22 has been assigned a threat score of 280/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
📊 Threat Analysis
IP address 104.46.226.22 has been traced to Osaka, Japan, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 2 days in our monitoring system, producing 65 flagged requests at a rate of ~32.5/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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 110 flagged addresses, Japan 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
💡 TLS Fingerprinting (JA3/JA4)
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
💡 Command Injection Techniques
Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.