ABUSE.MOM
THREAT REPORT

IP Threat Report
196.51.163.161

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 16:14:07
First seen: 2026-02-17 17:25:05
Last seen: 2026-02-17 17:26:16
85

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 85/100. Total malicious requests observed: 3.

DANGER_PATHRATIO_404REDIRECT_PROBEREFERERIMPORT
01

Geolocation & Classification

IP Address
196.51.163.161
Type
Hosting
Country
🇺🇸 United States
City
Providence
ISP
DynaNode LLC
Organization
E-Com Cloud Solution Co., Ltd
Autonomous System
AS400463 DynaNode LLC
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 4Medium-risk: admin panels, config files+40
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Σ = 85
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-02-17 17:25:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 4 (+40), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-02-17 17:26:16
Last malicious request observed
Total score reached: 85/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DynaNode LLC
AS400463 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 196.51.163.161 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 196.51.163.161 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (3)
PortServiceRiskDescription
80HTTPLowHTTP web server — standard web traffic
8080HTTP-AltLowHTTP alternative port — often used for admin panels or proxies
8800UnknownLowService on port 8800
KNOWN VULNERABILITIES (CVE) (56)
CVE IDLink
CVE-2021-28116NVD →
CVE-2023-46847NVD →
CVE-2019-12522NVD →
CVE-2021-31807NVD →
CVE-2024-37894NVD →
CVE-2018-19131NVD →
CVE-2020-25097NVD →
CVE-2025-59362NVD →
CVE-2024-45802NVD →
CVE-2020-15811NVD →
CVE-2019-18678NVD →
CVE-2023-46728NVD →
CVE-2018-1000024NVD →
CVE-2023-49288NVD →
CVE-2019-12529NVD →
CVE-2016-10003NVD →
CVE-2020-8449NVD →
CVE-2021-28652NVD →
CVE-2019-18676NVD →
CVE-2019-12520NVD →
CVE-2019-13345NVD →
CVE-2021-28651NVD →
CVE-2020-8517NVD →
CVE-2021-33620NVD →
CVE-2025-62168NVD →
+31 more

🔴 This host has 56 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.

DETECTED TECHNOLOGIES
squid-cache:squid:3.5.20

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
Spamhaus ZEN

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

196.51.163.161 has been assigned a threat score of 85/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:

Path Enumeration

📊 Threat Analysis

196.51.163.161 is registered in Providence, United States, operating on the network of DynaNode LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 1 days, this IP generated 3 malicious requests, averaging approximately 3 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. United States currently accounts for 198 blocked IPs in our database, making it a significant source of malicious traffic. A threat score of 85/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.

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.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS400463

156.241.212.110 (130)196.51.9.71 (130)196.51.88.191 (105)196.51.57.202 (105)196.51.7.223 (105)View all →
12

Security Intelligence

💡 Brute Force Attack Mechanics

Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

🔍 Check Any IP Address

Share this report: