IP Threat Report
174.138.93.176
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 |
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 174.138.93.176 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 174.138.93.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
⚙️ General Security
Add 174.138.93.176 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
Neighbors in 174.138.93.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 |
| CVE ID | Link |
|---|---|
| CVE-2025-32728 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2018-15473 | NVD → |
| CVE-2018-15919 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2019-6111 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2019-6110 | NVD → |
| CVE-2018-20685 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2019-6109 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2017-15906 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2016-20012 | NVD → |
🔴 This host has 20 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
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
174.138.93.176 has been assigned a threat score of 100/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
📊 Threat Analysis
174.138.93.176 is registered in Clifton, United States, operating on the network of DigitalOcean, LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 1 days in our monitoring system, producing 9 flagged requests at a rate of ~9/day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. United States currently accounts for 129 blocked IPs in our database, making it a significant source of malicious traffic. A score of 100/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.
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 →Security Intelligence
💡 HTTP Header Analysis for Threat Detection
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
💡 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.