
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | 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 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block scanning from 196.51.206.217: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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 |
|---|---|---|---|
| 8000 | Unknown | Low | Service on port 8000 |
| 8800 | Unknown | Low | Service on port 8800 |
| CVE ID | Link |
|---|---|
| CVE-2020-24606 | NVD → |
| CVE-2020-15811 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2019-12522 | NVD → |
| CVE-2016-10003 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2018-19131 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2019-18678 | NVD → |
| CVE-2020-25097 | NVD → |
🔴 Security scanning identified 59 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
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.
196.51.206.217 has been assigned a threat score of 105/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:
Threat intelligence analysis has linked 196.51.206.217 to malicious activity originating from Ashburn, United States, operating on the network of DynaNode LLC. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/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 IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 198 flagged addresses, United States represents a significant presence in our threat database. A score of 105/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.
SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.