IP Threat Report
158.158.33.103
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: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 42 | 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: 38 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 42 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 63 | Medium-risk: admin panels, config files | +60 | |
| Burst: 34 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 84 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 41 | Medium-risk: admin panels, config files | +60 | |
| Burst: 31 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 39 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 29 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 63 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 26 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 59 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 25 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 24 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 62 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 22 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 33 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 28 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 60 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 40 | Medium-risk: admin panels, config files | +60 | |
| Burst: 36 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 57 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 33 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 30 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 27 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 32 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +0 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 46 | Medium-risk: admin panels, config files | +60 | |
| Burst: 40 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 46 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Burst: 17 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 18 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 12 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Burst: 15 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 15 | Medium-risk: admin panels, config files | +60 | |
| Burst: 24 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 9 | Medium-risk: admin panels, config files | +60 | |
| Burst: 7 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 18 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 8 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 10 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 12 | Medium-risk: admin panels, config files | +60 | |
| Burst: 16 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 8 | Medium-risk: admin panels, config files | +60 | |
| Burst: 9 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 10 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 74 | Medium-risk: admin panels, config files | +60 | |
| Burst: 14 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 45 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 15 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 21 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 54 | Medium-risk: admin panels, config files | +60 | |
| Burst: 81 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 13 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 47 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 27 | Medium-risk: admin panels, config files | +60 | |
| Burst: 27 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 49 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 48 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 43 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 33 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 22 | Medium-risk: admin panels, config files | +60 | |
| Burst: 22 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 158.158.33.103 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 158.158.33.103: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Directory Scan Defense
IP 158.158.33.103 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 158.158.33.103.
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
158.158.33.103 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
Threat intelligence analysis has linked 158.158.33.103 to malicious activity originating from Madrid, Spain, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Over a period of 7 days, this IP generated 160 malicious requests, averaging approximately 22.9 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. 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
💡 User-Agent Analysis Techniques
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
💡 VPN Exit Node Reputation
VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.