ABUSE.MOM
THREAT REPORT

IP Threat Report
166.19.88.33

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-14 16:31:03
First seen: 2026-08-23 16:03:39
Last seen: 2026-08-30 01:03:24
95

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
166.19.88.33
Type
Hosting
Country
🇺🇸 United States
City
Roseland
ISP
CoreWeave, Inc
Organization
CoreWeave, Inc
Autonomous System
AS33425 CoreWeave, Inc
Hit Count
277
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 160
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-08-23 16:03:39
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger strong hits: 2 (+50), Danger strong hits: 3 (+75)
2026-08-30 01:03:24
Last malicious request observed
Total score reached: 95/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

CoreWeave, Inc
AS33425 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

07

Neighbors in 166.19.88.0/24

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

09

Blacklist Status (DNSBL)

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

✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

166.19.88.33 has been assigned a threat score of 95/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

The address 166.19.88.33 originates from Roseland, United States, operating on the network of CoreWeave, Inc. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 6 days, this IP generated 277 malicious requests, averaging approximately 46.2 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 111 blocked IPs in our database, making it a significant source of malicious traffic. At 95/100, this is an extremely high-risk address. All traffic should be considered hostile.

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.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS33425

166.19.88.43 (135)166.19.88.26 (135)166.19.88.47 (125)166.19.88.55 (120)166.19.88.11 (120)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 Residential Proxy Networks

Residential proxies route traffic through real home internet connections, making malicious traffic appear to come from legitimate users. Some networks install proxy software bundled with free applications, unknowingly conscripting millions of devices.

🔍 Check Any IP Address

Share this report: