
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 318 | Medium-risk: admin panels, config files | +60 | |
| Burst: 37 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 111 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 45 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 128 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 212 | 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: 113 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 41 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 141 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 33 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 107 req / 10s | Abnormally fast request rate — automated scanning | +35 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Address UA spoofing from 158.158.35.147: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
IP 158.158.35.147 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
IP 158.158.35.147 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.
158.158.35.147 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:
Our monitoring infrastructure has identified 158.158.35.147, geolocated to Madrid, Spain, operating on the network of Microsoft Corporation, as a source of suspicious network activity. During its 1-day observation window, we recorded 5 hostile requests from this IP — roughly 5 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 101 flagged addresses, Spain represents a significant presence in our threat database. 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.
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.
IP geolocation databases provide approximate locations with varying accuracy. City-level geolocation is typically 50-80% accurate, while country-level exceeds 95%. VPNs, proxies, and mobile networks further reduce reliability, making geolocation a useful but imperfect intelligence signal.