IP Threat Report
74.249.149.76
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: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 732 | Medium-risk: admin panels, config files | +60 | |
| Burst: 37 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 126 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 244 | Medium-risk: admin panels, config files | +60 | |
| Burst: 19 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 66 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 366 | Medium-risk: admin panels, config files | +60 | |
| Burst: 17 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 55 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 18 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 64 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 56 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 88 | 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: 69 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 20 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 71 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 72 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 156 | Medium-risk: admin panels, config files | +60 | |
| Burst: 68 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 63 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 67 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 61 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 |
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.249.149.76 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.249.149.76: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Traffic Flood Defense
IP 74.249.149.76 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🔎 Path Enumeration Protection
Block scanning from 74.249.149.76: 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
74.249.149.76 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
Our monitoring infrastructure has identified 74.249.149.76, geolocated to Des Moines, United States, operating on the network of Microsoft Corporation, as a source of suspicious network activity. Our sensors captured 16 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~16 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. Our records show 101 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. 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
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →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.
💡 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.