
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 49 | Medium-risk: admin panels, config files | +60 | |
| Burst: 19 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 58 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 19 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 48 | Medium-risk: admin panels, config files | +60 | |
| Burst: 57 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 204 | Medium-risk: admin panels, config files | +60 | |
| Burst: 66 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 18 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 46 | Medium-risk: admin panels, config files | +60 | |
| Burst: 55 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 40 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 107 | Medium-risk: admin panels, config files | +60 | |
| Burst: 63 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 67 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 68 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 118 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 371 | Medium-risk: admin panels, config files | +60 | |
| Burst: 69 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 65 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 27 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 207 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 31 | Medium-risk: admin panels, config files | +60 | |
| Burst: 41 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 51 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 5 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 75 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 11 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 34 | Medium-risk: admin panels, config files | +60 | |
| Burst: 43 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 47 | Medium-risk: admin panels, config files | +60 | |
| Burst: 56 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 15 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 55 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 22 | Medium-risk: admin panels, config files | +60 | |
| Burst: 24 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 64 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 21 | Medium-risk: admin panels, config files | +60 | |
| Burst: 23 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.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.198.83.136.
Block scanning from 20.198.83.136: 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 |
|---|---|---|---|
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 9000 | Unknown | Low | Service on port 9000 |
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.198.83.136 has been assigned a threat score of 255/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:
20.198.83.136 is registered in Pune, India, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 50 malicious requests from this address across a 4-day span, reflecting a sustained attack cadence of ~12.5 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. Two attack patterns were identified (Request Flooding and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 101 malicious IPs originating from India, positioning it as a significant contributor to global threat activity. 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.
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.
Advanced techniques enable threat detection while minimizing privacy impact. Encrypted DNS, differential privacy in analytics, and federated learning for threat models allow effective security monitoring without unnecessary surveillance of legitimate user behavior.