
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 74 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 294 | Medium-risk: admin panels, config files | +60 | |
| Burst: 15 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 53 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 52 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 49 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 293 | 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: 55 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 99 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 441 | Medium-risk: admin panels, config files | +60 | |
| Burst: 50 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 105 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 44 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 189 | Medium-risk: admin panels, config files | +60 | |
| Burst: 14 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 49 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 65 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 256 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 38 | Medium-risk: admin panels, config files | +60 | |
| Burst: 46 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 54 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 114 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 402 | Medium-risk: admin panels, config files | +60 |
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.212.80.137 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
IP 20.212.80.137 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
IP 20.212.80.137 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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.212.80.137 has been assigned a threat score of 280/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
Threat intelligence analysis has linked 20.212.80.137 to malicious activity originating from Singapore, Singapore, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. During its 2-day observation window, we recorded 16 hostile requests from this IP — roughly 8 per day on average. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 208 flagged addresses, Singapore represents a significant presence in our threat database. A score of 280/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
Network telescopes monitor large blocks of unused IP address space. Since no legitimate traffic should reach these addresses, all observed traffic represents scanning, backscatter from spoofed attacks, or misconfiguration — providing pure signal for threat analysis.