
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block 93.166.103.102 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
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.
93.166.103.102 has been assigned a threat score of 95/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
Our monitoring infrastructure has identified 93.166.103.102, geolocated to Silkeborg, DK, operating on the network of TDC Holding A/S, as a source of suspicious network activity. Our sensors captured 102 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~51 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Our records show 54 malicious IPs originating from DK, positioning it as a notable contributor to global threat activity. With a threat score of 95/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.
Proper network segmentation limits the blast radius of breaches. Even if attackers compromise one segment, properly configured network boundaries prevent lateral movement to critical systems, databases, and administrative interfaces.