ABUSE.MOM
THREAT REPORT

IP Threat Report
8.210.224.56

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:21:51
First seen: 2026-03-20 10:00:06
Last seen: 2026-03-20 10:00:06
145

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
8.210.224.56
Type
Residential
Country
🇭🇰 Hong Kong
City
Hong Kong
ISP
Alibaba (US) Technology Co., Ltd.
Organization
Alibaba.com Singapore E-Commerce Private Limited
Autonomous System
AS45102 Alibaba (US) Technology Co., Ltd.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
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
Σ = 145
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-03-20 10:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 10 (+100), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-03-20 10:00:06
Last malicious request observed
Total score reached: 145/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Alibaba (US) Technology Co., Ltd.
AS45102 · 🇭🇰 Hong Kong
06

Recommendations

Actions taken & recommended

  • IP 8.210.224.56 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 8.210.224.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

Block scanning from 8.210.224.56: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

07

Neighbors in 8.210.224.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

08

Open Ports & Services

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

OPEN PORTS (1)
PortServiceRiskDescription
22SSHLowSecure Shell — common brute force target for remote access
KNOWN VULNERABILITIES (CVE) (20)
CVE IDLink
CVE-2021-41617NVD →
CVE-2023-51385NVD →
CVE-2018-20685NVD →
CVE-2021-36368NVD →
CVE-2023-38408NVD →
CVE-2023-48795NVD →
CVE-2020-15778NVD →
CVE-2020-14145NVD →
CVE-2025-26465NVD →
CVE-2025-32728NVD →
CVE-2019-6111NVD →
CVE-2007-2768NVD →
CVE-2023-51767NVD →
CVE-2018-15919NVD →
CVE-2017-15906NVD →
CVE-2016-20012NVD →
CVE-2008-3844NVD →
CVE-2019-6110NVD →
CVE-2019-6109NVD →
CVE-2018-15473NVD →

🔴 Security scanning identified 20 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.

DETECTED TECHNOLOGIES
openbsd:openssh:7.4

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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

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

Path Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 8.210.224.56 to malicious activity originating from Hong Kong, Hong Kong, operating on the network of Alibaba (US) Technology Co., Ltd.. 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. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 88 malicious IPs originating from Hong Kong, positioning it as a notable contributor to global threat activity. With a threat score of 145/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇭🇰 Top threats from Hong Kong

8.217.181.151 (215)43.99.86.17 (215)47.238.141.179 (215)47.238.29.109 (215)43.99.41.243 (215)View all →

🏢 Same network: AS45102

8.213.218.53 (305)47.237.199.253 (300)8.215.205.243 (265)198.11.183.50 (220)8.217.181.151 (215)View all →
12

Security Intelligence

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

💡 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: