
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 11/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 12/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 32/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 36/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 37/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 108 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 136 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 28 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 32 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 36 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 40 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 54 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 64 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 71 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 11 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 15 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 37 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 20.222.2.83 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.222.2.83.
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.222.2.83 has been assigned a threat score of 255/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:
The address 20.222.2.83 originates from Tokyo, Japan, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 893 malicious requests, averaging approximately 893 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 dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 101 flagged addresses, Japan represents a significant presence in our threat database. With a threat score of 255/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Analyzing network flows (NetFlow, sFlow, IPFIX) provides visibility into traffic patterns without inspecting packet contents. Flow data reveals scanning activity, data exfiltration, lateral movement, and command-and-control channels at scale.