IP Threat Report
23.229.32.61
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| 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: 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 23.229.32.61 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 23.229.32.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 23.229.32.61: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Neighbors in 23.229.32.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 |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 3128 | Unknown | Low | Service on port 3128 |
| 8000 | Unknown | Low | Service on port 8000 |
| 8800 | Unknown | Low | Service on port 8800 |
| 21242 | Unknown | Low | Service on port 21242 |
| 52931 | Unknown | Low | Service on port 52931 |
| CVE ID | Link |
|---|---|
| CVE-2025-54574 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2019-12519 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2019-12525 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2020-11945 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2019-18678 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2019-12526 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2016-10003 | NVD → |
| CVE-2019-12521 | NVD → |
🔴 This host has 56 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
23.229.32.61 has been assigned a threat score of 70/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 23.229.32.61, located in Buffalo, United States, operating on the network of B2 Net Solutions Inc., has been classified as malicious by our automated threat scoring engine. The address has been active for 4 days in our monitoring system, producing 2 flagged requests at a rate of ~0.5/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. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 183 flagged addresses, United States represents a significant presence in our threat database. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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
💡 Vulnerability Scanning Explained
Vulnerability scanning is the automated process of probing web applications for known weaknesses. Attackers use tools like Nuclei, Nikto, and ZAP to test thousands of hosts per hour, looking for exposed configuration files, outdated software, and default credentials.
💡 Content Delivery Network Risks
CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.