IP Threat Report
161.35.38.220
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 |
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 161.35.38.220 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 161.35.38.220 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Directory Scan Defense
IP 161.35.38.220 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 993 | IMAPS | Low | Service on port 993 |
| CVE ID | Link |
|---|---|
| CVE-2022-26377 | NVD → |
| CVE-2019-1563 | NVD → |
| CVE-2024-38472 | NVD → |
| CVE-2017-3737 | NVD → |
| CVE-2023-0464 | NVD → |
| CVE-2024-43394 | NVD → |
| CVE-2019-1559 | NVD → |
| CVE-2014-0098 | NVD → |
| CVE-2022-1292 | NVD → |
| CVE-2018-0732 | NVD → |
| CVE-2022-0778 | NVD → |
| CVE-2024-47252 | NVD → |
| CVE-2023-0215 | NVD → |
| CVE-2021-44790 | NVD → |
| CVE-2024-3566 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2014-0226 | NVD → |
| CVE-2022-31628 | NVD → |
| CVE-2018-17199 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2023-5678 | NVD → |
| CVE-2019-10092 | NVD → |
| CVE-2024-42516 | NVD → |
| CVE-2019-1551 | NVD → |
🔴 This host has 149 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
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
161.35.38.220 has been assigned a threat score of 120/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 161.35.38.220, located in Slough, United Kingdom, operating on the network of DigitalOcean, LLC, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 3 malicious requests, averaging approximately 3 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. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 103 malicious IPs originating from United Kingdom, positioning it as a significant contributor to global threat activity. A score of 120/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
🇬🇧 Top threats from United Kingdom
104.28.208.60 (340)104.28.240.60 (340)91.230.225.3 (305)45.86.203.224 (305)45.86.203.35 (305)View all →Security Intelligence
💡 HTTP Header Analysis for Threat Detection
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
💡 Prototype Pollution Attacks
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.