
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Foreign referer | Referer from unrelated external domain | +10 |
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 18 malicious IPs from this autonomous system.
Block scanning from 102.252.15.0: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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.
102.252.15.0 has been assigned a threat score of 60/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:
Threat intelligence analysis has linked 102.252.15.0 to malicious activity originating from Durban, South Africa, operating on the network of Telkom SA Ltd.. The address has been under observation since its initial detection. Our sensors captured 84 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~28 requests per day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 260 flagged addresses, South Africa represents a significant presence in our threat database. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
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.
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.