IP Threat Report
104.46.216.98
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: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 209 | 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: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 40 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 45 | Medium-risk: admin panels, config files | +60 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 37 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 69 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 235 | Medium-risk: admin panels, config files | +60 | |
| Burst: 39 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 28 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 222 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 40 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 128 | Medium-risk: admin panels, config files | +60 | |
| 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 | |
| Danger strong hits: 17 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 117 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger strong hits: 51 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 233 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 222 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 443 | Medium-risk: admin panels, config files | +60 | |
| Burst: 38 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 | |
| Danger strong hits: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 126 | Medium-risk: admin panels, config files | +60 | |
| Burst: 43 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 72 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 295 | Medium-risk: admin panels, config files | +60 | |
| Burst: 44 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 102 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 419 | Medium-risk: admin panels, config files | +60 | |
| Burst: 13 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 45 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 125 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 240 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 97 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 203 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 301 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 664 | 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 | |
| Burst: 46 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 79 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 223 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 277 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 101 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 414 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 227 | Medium-risk: admin panels, config files | +60 | |
| Burst: 42 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 41 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 53 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 116 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 87 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 224 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 65 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 48 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 109 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 240 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 658 | Medium-risk: admin panels, config files | +60 | |
| Burst: 35 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 104.46.216.98 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 104.46.216.98 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Path Enumeration Protection
Block scanning from 104.46.216.98: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 104.46.216.98 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
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.216.98 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
The address 104.46.216.98 originates from Tokyo, Japan, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 52 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~17.3 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Our records show 15 malicious IPs originating from Japan, positioning it as a notable contributor to global threat activity. 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
💡 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.
💡 Subnet-Level vs IP-Level Blocking
When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.