IP Threat Report
165.22.240.105
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 |
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 165.22.240.105 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 User-Agent Anomaly Defense
IP 165.22.240.105 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Path Enumeration Protection
Block scanning from 165.22.240.105: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 165.22.240.105.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 10001 | Unknown | Low | Service on port 10001 |
| 10002 | Unknown | Low | Service on port 10002 |
| 10003 | Unknown | Low | Service on port 10003 |
| 10008 | Unknown | Low | Service on port 10008 |
| 10014 | Unknown | Low | Service on port 10014 |
| 10249 | Unknown | Low | Service on port 10249 |
| 10250 | Unknown | Low | Service on port 10250 |
| 10348 | Unknown | Low | Service on port 10348 |
| 11211 | Unknown | Low | Service on port 11211 |
| 12000 | Unknown | Low | Service on port 12000 |
| 12016 | Unknown | Low | Service on port 12016 |
| 12124 | Unknown | Low | Service on port 12124 |
| 12159 | Unknown | Low | Service on port 12159 |
| 12192 | Unknown | Low | Service on port 12192 |
| 12251 | Unknown | Low | Service on port 12251 |
| 12260 | Unknown | Low | Service on port 12260 |
| 12334 | Unknown | Low | Service on port 12334 |
| 12337 | Unknown | Low | Service on port 12337 |
| 12354 | Unknown | Low | Service on port 12354 |
| 12397 | Unknown | Low | Service on port 12397 |
| 12410 | Unknown | Low | Service on port 12410 |
| 12465 | Unknown | Low | Service on port 12465 |
| 12466 | Unknown | Low | Service on port 12466 |
| 12503 | Unknown | Low | Service on port 12503 |
| 12535 | Unknown | Low | Service on port 12535 |
| 12547 | Unknown | Low | Service on port 12547 |
| 12557 | Unknown | Low | Service on port 12557 |
| 12571 | Unknown | Low | Service on port 12571 |
| 13084 | Unknown | Low | Service on port 13084 |
| 13579 | Unknown | Low | Service on port 13579 |
| 13718 | Unknown | Low | Service on port 13718 |
| 14875 | Unknown | Low | Service on port 14875 |
| 14903 | Unknown | Low | Service on port 14903 |
| 15123 | Unknown | Low | Service on port 15123 |
| 16010 | Unknown | Low | Service on port 16010 |
| 16080 | Unknown | Low | Service on port 16080 |
| 16093 | Unknown | Low | Service on port 16093 |
| 16401 | Unknown | Low | Service on port 16401 |
| 16993 | Unknown | Low | Service on port 16993 |
| 17082 | Unknown | Low | Service on port 17082 |
| 18003 | Unknown | Low | Service on port 18003 |
| 18036 | Unknown | Low | Service on port 18036 |
| 18047 | Unknown | Low | Service on port 18047 |
| 18051 | Unknown | Low | Service on port 18051 |
| 18053 | Unknown | Low | Service on port 18053 |
| 18061 | Unknown | Low | Service on port 18061 |
| 18068 | Unknown | Low | Service on port 18068 |
| 18072 | Unknown | Low | Service on port 18072 |
| 19071 | Unknown | Low | Service on port 19071 |
| 19080 | Unknown | Low | Service on port 19080 |
| 19527 | Unknown | Low | Service on port 19527 |
| 30011 | Unknown | Low | Service on port 30011 |
| 30473 | Unknown | Low | Service on port 30473 |
| 30479 | Unknown | Low | Service on port 30479 |
| 31337 | Unknown | Low | Service on port 31337 |
| 31380 | Unknown | Low | Service on port 31380 |
| 33060 | Unknown | Low | Service on port 33060 |
| 33700 | Unknown | Low | Service on port 33700 |
| 35554 | Unknown | Low | Service on port 35554 |
| 35874 | Unknown | Low | Service on port 35874 |
| 37777 | Unknown | Low | Service on port 37777 |
| 38779 | Unknown | Low | Service on port 38779 |
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
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
165.22.240.105 has been assigned a threat score of 215/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 165.22.240.105, geolocated to Singapore, Singapore, operating on the network of DigitalOcean, LLC, as a source of suspicious network activity. Our sensors captured 2 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~2 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 41 flagged addresses, Singapore represents a notable presence in our threat database. A score of 215/100 places this address in the top tier of severity. Block and investigate any historical connections.
This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
Related Threats
Security Intelligence
💡 User-Agent Analysis Techniques
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
💡 Subnet-Level vs IP-Level Blocking
When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.