
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
We have detected 6567 malicious IPs from this autonomous system.
Block 104.234.32.14 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.
104.234.32.14 has been assigned a threat score of 100/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
Threat intelligence analysis has linked 104.234.32.14 to malicious activity originating from Chicago, United States, operating on the network of F.N.S. HOLDINGS LIMITED. The address has been under observation since its initial detection. Our sensors captured 204 malicious requests from this address across a 18-day span, reflecting a sustained attack cadence of ~11.3 requests per day. United States currently accounts for 36,299 blocked IPs in our database, making it a major source of malicious traffic. At 100/100, this is an extremely high-risk address. All traffic should be considered hostile.
Watering hole attacks compromise websites frequently visited by target organizations. Rather than attacking targets directly, adversaries infect trusted resources, exploiting the inherent trust users place in regularly visited sites.
Modern HTTP protocols introduce new attack surfaces including stream multiplexing abuse, header compression attacks (HPACK bombing), and rapid reset attacks. Security tools must evolve to handle these protocol-specific threats effectively.