ABUSE.MOM
THREAT REPORT

IP Threat Report
104.238.36.205

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 17:28:23
First seen: 2026-02-17 17:25:05
Last seen: 2026-03-14 00:00:08
140

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERERIMPORTBURST
01

Geolocation & Classification

IP Address
104.238.36.205
Type
Residential
Country
🇺🇸 United States
City
New York
ISP
Web2Objects LLC
Organization
Web2Objects LLC
Autonomous System
AS62874 Web2Objects LLC
Hit Count
7
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 6Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 140
03

Observed Activity

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

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

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

04

Timeline

2026-02-17 17:25:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 6 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-03-14 00:00:08
Last malicious request observed
Total score reached: 140/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Web2Objects LLC
AS62874 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 104.238.36.205 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

🔎 Path Enumeration Protection

Block scanning from 104.238.36.205: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 104.238.36.205.

09

Blacklist Status (DNSBL)

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

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

104.238.36.205 has been assigned a threat score of 140/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:

Path EnumerationRequest Flooding

📊 Threat Analysis

Network traffic from 104.238.36.205, located in New York, United States, operating on the network of Web2Objects LLC, has been classified as malicious by our automated threat scoring engine. Our sensors captured 7 malicious requests from this address across a 24-day span, reflecting a sustained attack cadence of ~0.3 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. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 121 flagged addresses, United States represents a significant presence in our threat database. At 140/100, this is an extremely high-risk address. All traffic should be considered hostile.

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: AS62874

45.41.130.12 (153)104.238.37.234 (150)45.56.174.2 (150)45.61.122.106 (140)45.56.173.209 (140)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.

💡 IoT Device Compromise Patterns

Internet of Things devices are prime targets for botnet recruitment due to weak default credentials, infrequent updates, and always-on connectivity. Compromised IoT devices generate persistent scanning and attack traffic without their owners knowledge.

🔍 Check Any IP Address

Share this report: