IP Threat Report
158.158.35.221
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: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 264 | Medium-risk: admin panels, config files | +60 | |
| Burst: 41 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 142 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 190 | 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: 36 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 118 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.35.221 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 158.158.35.0/24
- 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.35.221: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 158.158.35.221.
🔎 Directory Scan Defense
IP 158.158.35.221 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Neighbors in 158.158.35.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.35.221 has been assigned a threat score of 280/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
📊 Threat Analysis
Threat intelligence analysis has linked 158.158.35.221 to malicious activity originating from Madrid, Spain, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 2 hostile requests from this IP — roughly 2 per day on average. 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 114 flagged addresses, Spain represents a significant presence in our threat database. 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
💡 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.
💡 Memory Safety and Buffer Overflows
Buffer overflow vulnerabilities remain relevant in C/C++ applications despite decades of mitigation efforts. Modern protections like ASLR, stack canaries, and DEP reduce exploitability but determined attackers continue finding bypass techniques.