
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 56/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 56/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 58/10s | 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 223 malicious IPs from this autonomous system.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 76.105.205.127.
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.
76.105.205.127 has been assigned a threat score of 80/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
The address 76.105.205.127 originates from Salem, United States, operating on the network of Comcast Cable Communications, LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 345 malicious requests from this address across a 9-day span, reflecting a sustained attack cadence of ~38.3 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 36,323 malicious IPs originating from United States, positioning it as a major contributor to global threat activity. 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.
Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.