ABUSE.MOM
THREAT REPORT

IP Threat Report
23.236.241.135

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 01:49:06
First seen: 2026-04-20 16:00:06
Last seen: 2026-04-20 16:00:06
70

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 70/100. Total malicious requests observed: 1.

DANGER_PATHREDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
23.236.241.135
Type
Residential
Country
🇺🇸 United States
City
Los Angeles
ISP
HostPapa
Organization
B2 Net Solutions Inc
Autonomous System
AS36352 HostPapa
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 4Medium-risk: admin panels, config files+40
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Σ = 70
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-04-20 16:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 4 (+40), Probe pattern 302->404 same path (+20), Foreign referer seen (+10)
2026-04-20 16:00:06
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

HostPapa
AS36352 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 23.236.241.135 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.236.241.0/24
  • 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 23.236.241.135 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

07

Neighbors in 23.236.241.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (6)
PortServiceRiskDescription
80HTTPLowHTTP web server — standard web traffic
3128UnknownLowService on port 3128
8000UnknownLowService on port 8000
8080HTTP-AltLowHTTP alternative port — often used for admin panels or proxies
8800UnknownLowService on port 8800
21242UnknownLowService on port 21242
KNOWN VULNERABILITIES (CVE) (59)
CVE IDLink
CVE-2025-62168NVD →
CVE-2023-49288NVD →
CVE-2020-24606NVD →
CVE-2019-18679NVD →
CVE-2019-18677NVD →
CVE-2018-1000024NVD →
CVE-2019-12524NVD →
CVE-2023-46847NVD →
CVE-2021-31807NVD →
CVE-2023-46728NVD →
CVE-2021-33620NVD →
CVE-2020-14058NVD →
CVE-2024-37894NVD →
CVE-2020-15049NVD →
CVE-2019-12525NVD →
CVE-2019-12529NVD →
CVE-2025-59362NVD →
CVE-2020-25097NVD →
CVE-2019-12520NVD →
CVE-2019-13345NVD →
CVE-2021-31806NVD →
CVE-2026-33515NVD →
CVE-2026-33526NVD →
CVE-2019-12523NVD →
CVE-2019-12521NVD →
+34 more

🔴 This host has 59 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.

DETECTED TECHNOLOGIES
squid-cache:squid:3.5.20

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

23.236.241.135 has been assigned a threat score of 70/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

23.236.241.135 is registered in Los Angeles, United States, operating on the network of HostPapa. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 200 flagged addresses, United States represents a significant presence in our threat database. At 70/100, this IP warrants immediate defensive action.

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.

11

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 →

🏢 Same network: AS36352

23.94.40.119 (318)172.245.95.40 (280)23.94.28.183 (255)192.227.215.35 (255)172.245.214.62 (245)View all →
12

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.

💡 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.

🔍 Check Any IP Address

Share this report: