
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 80 | 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: 44 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 82 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 12 | Medium-risk: admin panels, config files | +60 | |
| Burst: 10 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 18 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 18 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 15 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Burst: 9 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 7 | Medium-risk: admin panels, config files | +60 | |
| Burst: 10 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 60 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 122 | Medium-risk: admin panels, config files | +60 | |
| Burst: 58 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 156 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 68 | Medium-risk: admin panels, config files | +60 | |
| Burst: 52 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 102 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 66 | Medium-risk: admin panels, config files | +60 | |
| Burst: 61 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 99 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 16 | Medium-risk: admin panels, config files | +60 | |
| Burst: 24 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 24 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 24 | Medium-risk: admin panels, config files | +60 | |
| Burst: 31 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 32 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 23 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 45 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 125 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.91.197.85 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
IP 20.91.197.85 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.91.197.85.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
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.91.197.85 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:
Network traffic from 20.91.197.85, located in Gävle, Sweden, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 27 malicious requests, averaging approximately 27 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 diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Our records show 101 malicious IPs originating from Sweden, 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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.