
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 20/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 20/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.
We have detected 313 malicious IPs from this autonomous system.
IP 89.109.47.177 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
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.
89.109.47.177 has been assigned a threat score of 80/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:
Network traffic from 89.109.47.177, located in Nizhniy Novgorod, Russia, operating on the network of Rostelecom networks, has been classified as malicious by our automated threat scoring engine. During its 5-day observation window, we recorded 118 hostile requests from this IP — roughly 23.6 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Russia currently accounts for 2,651 blocked IPs in our database, making it a major source of malicious traffic. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
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.
Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.