IP Threat Report
170.199.228.42
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 7 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 |
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 170.199.228.42 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 170.199.228.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 170.199.228.42: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Neighbors in 170.199.228.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 |
|---|---|---|---|
| 4444 | Unknown | Low | Service on port 4444 |
| 8000 | Unknown | Low | Service on port 8000 |
| CVE ID | Link |
|---|---|
| CVE-2023-49286 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-31806 | NVD → |
🔴 This host has 30 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
170.199.228.42 has been assigned a threat score of 105/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
170.199.228.42 is registered in Los Angeles, United States, operating on the network of Blazing SEO. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 4 malicious requests from this address across a 8-day span, reflecting a sustained attack cadence of ~0.5 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 208 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 105/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 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 Request Smuggling
Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.
💡 Botnet Command and Control Evolution
Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.