IP Threat Report
173.249.205.94
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 medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 |
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 173.249.205.94 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
🔎 Path Enumeration Protection
Block scanning from 173.249.205.94: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
| 33060 | Unknown | Low | Service on port 33060 |
⚠️ Network scanning reveals 1 dangerous service exposed on 173.249.205.94. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2025-50093 | NVD → |
| CVE-2025-50099 | NVD → |
| CVE-2025-50085 | NVD → |
| CVE-2025-50102 | NVD → |
| CVE-2025-50086 | NVD → |
| CVE-2025-50098 | NVD → |
| CVE-2025-50083 | NVD → |
| CVE-2025-50091 | NVD → |
| CVE-2025-23419 | NVD → |
| CVE-2025-50092 | NVD → |
| CVE-2025-50084 | NVD → |
| CVE-2025-50097 | NVD → |
| CVE-2025-50087 | NVD → |
| CVE-2025-50077 | NVD → |
| CVE-2025-50078 | NVD → |
| CVE-2023-44487 | NVD → |
| CVE-2025-50104 | NVD → |
| CVE-2025-50100 | NVD → |
| CVE-2025-50080 | NVD → |
| CVE-2026-21964 | NVD → |
| CVE-2025-50101 | NVD → |
| CVE-2025-50096 | NVD → |
| CVE-2025-50079 | NVD → |
| CVE-2025-50082 | NVD → |
| CVE-2025-50088 | NVD → |
🔴 Security scanning identified 26 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
173.249.205.94 has been assigned a threat score of 95/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
📊 Threat Analysis
IP address 173.249.205.94 has been traced to Phoenix, United States, operating on the network of tzulo, inc.. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 141 flagged addresses, United States represents a significant presence in our threat database. A score of 95/100 places this address in the top tier of severity. Block and investigate any historical connections.
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 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
💡 Prototype Pollution Attacks
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.
💡 GDPR and Threat Intelligence
Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.