IP Threat Report
135.235.197.113
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 135.235.197.113 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
⚙️ General Security
Add 135.235.197.113 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
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
135.235.197.113 has been assigned a threat score of 85/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
📊 Threat Analysis
The address 135.235.197.113 originates from Pune, India, operating on the network of MICROSOFT. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 6 days, this IP generated 1,353 malicious requests, averaging approximately 225.5 requests per day. Our records show 101 malicious IPs originating from India, positioning it as a significant contributor to global threat activity. A threat score of 85/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.
Related Threats
Security Intelligence
💡 Container Security Challenges
Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.
💡 Server-Side Request Forgery (SSRF)
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.