
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 115/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 134/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 148/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 165/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 168/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 170/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 172/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 189/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 64/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 69/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 70/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 88/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 91/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 95/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 99/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Danger medium hits: 7 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 100 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 109 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 113 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 127 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 131 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 173 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| UA bot: curl | Known bot/crawler User-Agent detected | +40 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 31.59.160.3 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Address UA spoofing from 31.59.160.3: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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.
31.59.160.3 has been assigned a threat score of 305/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 31.59.160.3, geolocated to Stockholm, Sweden, operating on the network of Miteflux Technologies Ltd, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 253 flagged requests at a rate of ~253/day. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 727 malicious IPs originating from Sweden, positioning it as a major contributor to global threat activity. At 305/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.