IP Threat Report
136.144.35.42
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 | |
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 |
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
Network Provider
Recommendations
Actions taken & recommended
- IP 136.144.35.42 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 136.144.35.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Directory Scan Defense
IP 136.144.35.42 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🤖 User-Agent Anomaly Defense
IP 136.144.35.42 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Neighbors in 136.144.35.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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
136.144.35.42 has been assigned a threat score of 100/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
📊 Threat Analysis
136.144.35.42 is registered in Trenton, United States, operating on the network of Latitude.sh. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 61 days, this IP generated 233 malicious requests, averaging approximately 3.8 requests per day. Classified as a VPN or proxy server, this IP serves as an anonymization layer. While VPNs have legitimate uses, this address has been observed routing clearly malicious traffic. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 231 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 100/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →Security Intelligence
💡 File Upload Vulnerabilities
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.
💡 Network Flow Analysis
Analyzing network flows (NetFlow, sFlow, IPFIX) provides visibility into traffic patterns without inspecting packet contents. Flow data reveals scanning activity, data exfiltration, lateral movement, and command-and-control channels at scale.