IP Threat Report
74.248.96.101
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 103/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 104/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 105/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 107/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 109/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 114/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 119/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 124/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 135/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 146/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 148/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 30/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 32/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 33/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 34/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 35/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 38/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 43/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 44/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 58/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 60/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 85/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 86/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 87/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 88/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 90/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 93/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 94/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 96/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 98/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 160 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 163 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 184 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 186 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 245 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 348 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 428 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 448 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 556 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 93 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 48 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 56 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 84 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +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 74.248.96.101 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
🔎 Path Enumeration Protection
Block scanning from 74.248.96.101: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 74.248.96.101 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🤖 User-Agent Anomaly Defense
IP 74.248.96.101 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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
74.248.96.101 has been assigned a threat score of 280/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
Threat intelligence analysis has linked 74.248.96.101 to malicious activity originating from Warsaw, Poland, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Our sensors captured 2,335 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~778.3 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. At 280/100, this is an extremely high-risk address. All traffic should be considered hostile.
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
💡 DDoS Mitigation Approaches
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
💡 Rate Limiting and Throttling Strategies
Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.