
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 19/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 20/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 21/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 22/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 23/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 64/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 65/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 67/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 68/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 70/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 71/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 74/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 1298 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 426 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 649 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 87 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 187 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 282 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 564 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block scanning from 20.104.234.28: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.104.234.28.
IP 20.104.234.28 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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.
20.104.234.28 has been assigned a threat score of 255/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:
Threat intelligence analysis has linked 20.104.234.28 to malicious activity originating from Toronto, Canada, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Our sensors captured 1,004 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~502 requests per day. 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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Canada currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 255/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.
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.
Hacktivism combines hacking skills with political or social motivations. DDoS campaigns, website defacements, and data leaks target organizations based on ideological disagreements, adding unpredictable threat actors to the landscape.