IP Threat Report
74.248.20.136
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: 50 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 418 | Medium-risk: admin panels, config files | +60 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 33 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 112 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 420 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 39 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 125 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 67 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 630 | Medium-risk: admin panels, config files | +60 | |
| Burst: 37 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 121 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 41 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 132 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 419 | Medium-risk: admin panels, config files | +60 | |
| Burst: 111 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 30 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 93 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 36 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 122 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 38 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 129 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 127 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 49 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 133 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 42 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 135 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 46 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 144 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 74.248.20.136 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 74.248.20.136: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Path Enumeration Protection
Block scanning from 74.248.20.136: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 74.248.20.136 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
74.248.20.136 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
IP address 74.248.20.136 has been traced to Warsaw, Poland, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 13 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~13 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Poland currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 280/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
💡 Log Correlation and SIEM Integration
Correlating logs across web servers, firewalls, DNS, and authentication systems reveals attack patterns invisible in individual log sources. Modern SIEM platforms use statistical analysis to connect related events across time and systems.