
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.
Block 170.199.229.236 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.
170.199.229.236 has been assigned a threat score of 105/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
Network traffic from 170.199.229.236, located in Los Angeles, United States, operating on the network of Blazing SEO, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 244 hostile requests from this IP — roughly 244 per day on average. Classified as a VPN or proxy server, this IP serves as an anonymization layer. While VPNs have legitimate uses, this address has been observed routing clearly malicious traffic. United States currently accounts for 128 blocked IPs in our database, making it a significant source of malicious traffic. At 105/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.
Passive DNS databases record historical DNS resolution data, enabling analysts to track domain changes, identify related infrastructure, and discover malicious domains sharing hosting with known threats. This historical context is invaluable for threat investigation.
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.