IP Threat Report
15.204.12.43
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Burst: 5 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 |
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 15.204.12.43 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
🔎 Directory Scan Defense
IP 15.204.12.43 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 15.204.12.43.
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 |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 2020 | Unknown | Low | Service on port 2020 |
| CVE ID | Link |
|---|---|
| CVE-2025-65082 | NVD → |
| CVE-2022-23943 | NVD → |
| CVE-2019-11358 | NVD → |
| CVE-2018-14040 | NVD → |
| CVE-2022-28615 | NVD → |
| CVE-2012-3526 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2018-20677 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2020-11023 | NVD → |
| CVE-2022-22721 | NVD → |
| CVE-2012-4360 | NVD → |
| CVE-2024-43204 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2023-25690 | NVD → |
| CVE-2024-38476 | NVD → |
| CVE-2022-28614 | NVD → |
| CVE-2020-11022 | NVD → |
| CVE-2024-38472 | NVD → |
| CVE-2023-38709 | NVD → |
| CVE-2018-20676 | NVD → |
| CVE-2015-9251 | NVD → |
| CVE-2022-31813 | NVD → |
🔴 This host has 64 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
15.204.12.43 has been assigned a threat score of 130/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
15.204.12.43 is registered in Hillsboro, United States, operating on the network of OVH SAS. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 2 days, this IP generated 4 malicious requests, averaging approximately 2 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. A score of 130/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
51.81.129.208 (160)142.44.205.40 (140)142.44.205.38 (140)142.44.205.42 (140)View all →Security Intelligence
💡 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.
💡 API Abuse and Enumeration
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.