IP Threat Report
8.219.175.223
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| 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 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 8.219.175.223 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.219.175.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 Bot Detection
Address UA spoofing from 8.219.175.223: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Path Enumeration Protection
Block scanning from 8.219.175.223: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Neighbors in 8.219.175.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Open Ports & Services
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 |
| 1013 | Unknown | Low | Service on port 1013 |
| 1023 | Unknown | Low | Service on port 1023 |
| 1080 | Unknown | Low | Service on port 1080 |
| 1153 | Unknown | Low | Service on port 1153 |
| 1200 | Unknown | Low | Service on port 1200 |
| 1224 | Unknown | Low | Service on port 1224 |
| 1244 | Unknown | Low | Service on port 1244 |
| 1249 | Unknown | Low | Service on port 1249 |
| 1291 | Unknown | Low | Service on port 1291 |
| 1344 | Unknown | Low | Service on port 1344 |
| 1370 | Unknown | Low | Service on port 1370 |
| 1443 | Unknown | Low | Service on port 1443 |
| 1471 | Unknown | Low | Service on port 1471 |
| 1557 | Unknown | Low | Service on port 1557 |
| 1577 | Unknown | Low | Service on port 1577 |
| 1599 | Unknown | Low | Service on port 1599 |
| 1723 | PPTP | Low | Service on port 1723 |
| 1741 | Unknown | Low | Service on port 1741 |
| 1800 | Unknown | Low | Service on port 1800 |
| 1911 | Unknown | Low | Service on port 1911 |
| 1925 | Unknown | Low | Service on port 1925 |
| 1950 | Unknown | Low | Service on port 1950 |
| 1952 | Unknown | Low | Service on port 1952 |
| 1962 | Unknown | Low | Service on port 1962 |
| 1967 | Unknown | Low | Service on port 1967 |
| 1970 | Unknown | Low | Service on port 1970 |
| 1981 | Unknown | Low | Service on port 1981 |
| CVE ID | Link |
|---|---|
| CVE-2017-15906 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2018-20685 | NVD → |
| CVE-2018-15473 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2019-6109 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2019-6110 | NVD → |
| CVE-2019-6111 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2018-15919 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2008-3844 | NVD → |
🔴 Security scanning identified 20 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.
Blacklist Status (DNSBL)
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.
Threat Analysis
8.219.175.223 has been assigned a threat score of 100/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 8.219.175.223, geolocated to Singapore, Singapore, operating on the network of Alibaba (US) Technology Co., Ltd., as a source of suspicious network activity. Our sensors captured 2 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~2 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Singapore currently accounts for 108 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 100/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.
Related Threats
🇸🇬 Top threats from Singapore
85.203.23.12 (340)85.203.23.31 (330)84.17.39.195 (325)192.166.246.30 (325)85.203.21.101 (320)View all →Security Intelligence
💡 TLS Fingerprinting (JA3/JA4)
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
💡 Server-Side Template Injection
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.