
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 15/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 15/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 6/2s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer | Referer from unrelated external domain | +10 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 46.138.250.165.
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.
46.138.250.165 has been assigned a threat score of 80/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
IP address 46.138.250.165 has been traced to Moscow, Russia, operating on the network of Moscow Local Telephone Network (PJSC MGTS). Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 10 days in our monitoring system, producing 464 flagged requests at a rate of ~46.4/day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 102 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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.
Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.