IP Threat Report
102.113.39.149
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Recommendations
Actions taken & recommended
- IP 102.113.39.149 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
⚙️ Defensive Recommendations
Block 102.113.39.149 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
Blacklist Status (DNSBL)
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.
Threat Analysis
102.113.39.149 has been assigned a threat score of 95/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
📊 Threat Analysis
IP address 102.113.39.149 has been traced to Vacoas, MU, operating on the network of MauritiusTelecom. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 914 malicious requests from this address across a 12-day span, reflecting a sustained attack cadence of ~76.2 requests per day. With 20 flagged addresses, MU represents a notable presence in our threat database. At 95/100, this is an extremely high-risk address. All traffic should be considered hostile.
Related Threats
Security Intelligence
💡 Autonomous System Analysis
Analyzing attack patterns at the AS (Autonomous System) level reveals which networks harbor the most malicious activity. Some ASes have abuse rates orders of magnitude higher than average, indicating lax enforcement of acceptable use policies.
💡 Server-Side Template Injection
SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.