
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block scanning from 170.199.228.181: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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.228.181 has been assigned a threat score of 75/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
Our monitoring infrastructure has identified 170.199.228.181, geolocated to Los Angeles, United States, operating on the network of Blazing SEO, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 325 flagged requests at a rate of ~325/day. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 208 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 75/100, this IP warrants immediate defensive action.
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.
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.
WAFs inspect HTTP traffic to block common attacks but require careful tuning. Overly aggressive rules cause false positives while permissive configurations miss attacks. Modern WAFs combine signature matching with behavioral analysis and machine learning.