IP Threat Report
139.180.7.214
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | 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 |
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 139.180.7.214 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 139.180.7.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 139.180.7.214: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Neighbors in 139.180.7.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 |
|---|---|---|---|
| 8000 | Unknown | Low | Service on port 8000 |
| CVE ID | Link |
|---|---|
| CVE-2021-31807 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2021-31808 | 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
139.180.7.214 has been assigned a threat score of 105/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
The address 139.180.7.214 originates from Chicago, United States, operating on the network of Sprious LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 201 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 105/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.
💡 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.