
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 87 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 200 | Medium-risk: admin panels, config files | +60 | |
| Burst: 23 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 83 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 160 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 816 | Medium-risk: admin panels, config files | +60 | |
| Burst: 47 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 168 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 60 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 272 | Medium-risk: admin panels, config files | +60 | |
| Burst: 22 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 52 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 274 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 18 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 58 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 63 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 202 | Medium-risk: admin panels, config files | +60 | |
| Burst: 17 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 58 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 204 | Medium-risk: admin panels, config files | +60 | |
| Burst: 59 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 116 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 306 | Medium-risk: admin panels, config files | +60 | |
| Burst: 77 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 84 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 61 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 19 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 63 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 24 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 87 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 50 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 172 | Medium-risk: admin panels, config files | +60 | |
| Burst: 57 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 70 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 160 | Medium-risk: admin panels, config files | +60 | |
| Burst: 68 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 73 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 171 | Medium-risk: admin panels, config files | +60 | |
| Burst: 74 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 75 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 21 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 72 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 165 | Medium-risk: admin panels, config files | +60 | |
| Burst: 67 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 78 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 69 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 81 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 73 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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.104.77.6 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.104.77.6.
Block scanning from 20.104.77.6: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 4064 | Unknown | Low | Service on port 4064 |
| 18021 | Unknown | Low | Service on port 18021 |
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
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.77.6 has been assigned a threat score of 280/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:
20.104.77.6 is registered in Toronto, Canada, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 21 malicious requests from this address across a 7-day span, reflecting a sustained attack cadence of ~3 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Our records show 101 malicious IPs originating from Canada, positioning it as a significant contributor to global threat activity. At 280/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.
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
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.