ABUSE.MOM
THREAT REPORT

IP Threat Report
172.161.1.105

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 13:47:32
First seen: 2026-08-07 02:20:42
Last seen: 2026-08-16 01:04:04
280

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 280/100. Total malicious requests observed: 2903.

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
172.161.1.105
Type
Hosting
Country
🇨🇭 Switzerland
City
Zurich
ISP
Microsoft
Organization
Microsoft Azure Cloud (switzerlandnorth)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
2903
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 102/10sAbnormally fast request rate — automated scanning+35
Burst 107/10sAbnormally fast request rate — automated scanning+35
Burst 109/10sAbnormally fast request rate — automated scanning+35
Burst 11/10sAbnormally fast request rate — automated scanning+35
Burst 11/2sAbnormally fast request rate — automated scanning+35
Burst 113/10sAbnormally fast request rate — automated scanning+35
Burst 116/10sAbnormally fast request rate — automated scanning+35
Burst 117/10sAbnormally fast request rate — automated scanning+35
Burst 118/10sAbnormally fast request rate — automated scanning+35
Burst 119/10sAbnormally fast request rate — automated scanning+35
Burst 121/10sAbnormally fast request rate — automated scanning+35
Burst 123/10sAbnormally fast request rate — automated scanning+35
Burst 127/10sAbnormally fast request rate — automated scanning+35
Burst 129/10sAbnormally fast request rate — automated scanning+35
Burst 130/10sAbnormally fast request rate — automated scanning+35
Burst 131/10sAbnormally fast request rate — automated scanning+35
Burst 133/10sAbnormally fast request rate — automated scanning+35
Burst 135/10sAbnormally fast request rate — automated scanning+35
Burst 136/10sAbnormally fast request rate — automated scanning+35
Burst 137/10sAbnormally fast request rate — automated scanning+35
Burst 140/10sAbnormally fast request rate — automated scanning+35
Burst 141/10sAbnormally fast request rate — automated scanning+35
Burst 142/10sAbnormally fast request rate — automated scanning+35
Burst 144/10sAbnormally fast request rate — automated scanning+35
Burst 146/10sAbnormally fast request rate — automated scanning+35
Burst 147/10sAbnormally fast request rate — automated scanning+35
Burst 148/10sAbnormally fast request rate — automated scanning+35
Burst 149/10sAbnormally fast request rate — automated scanning+35
Burst 152/10sAbnormally fast request rate — automated scanning+35
Burst 155/10sAbnormally fast request rate — automated scanning+35
Burst 160/10sAbnormally fast request rate — automated scanning+35
Burst 166/10sAbnormally fast request rate — automated scanning+35
Burst 174/10sAbnormally fast request rate — automated scanning+35
Burst 176/10sAbnormally fast request rate — automated scanning+35
Burst 184/10sAbnormally fast request rate — automated scanning+35
Burst 188/10sAbnormally fast request rate — automated scanning+35
Burst 190/10sAbnormally fast request rate — automated scanning+35
Burst 191/10sAbnormally fast request rate — automated scanning+35
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 33/2sAbnormally fast request rate — automated scanning+35
Burst 36/2sAbnormally fast request rate — automated scanning+35
Burst 37/2sAbnormally fast request rate — automated scanning+35
Burst 38/2sAbnormally fast request rate — automated scanning+35
Burst 39/2sAbnormally fast request rate — automated scanning+35
Burst 40/2sAbnormally fast request rate — automated scanning+35
Burst 42/2sAbnormally fast request rate — automated scanning+35
Burst 43/2sAbnormally fast request rate — automated scanning+35
Burst 44/2sAbnormally fast request rate — automated scanning+35
Burst 45/2sAbnormally fast request rate — automated scanning+35
Burst 46/2sAbnormally fast request rate — automated scanning+35
Burst 48/2sAbnormally fast request rate — automated scanning+35
Burst 49/2sAbnormally fast request rate — automated scanning+35
Burst 50/2sAbnormally fast request rate — automated scanning+35
Burst 51/2sAbnormally fast request rate — automated scanning+35
Burst 52/2sAbnormally fast request rate — automated scanning+35
Burst 53/2sAbnormally fast request rate — automated scanning+35
Burst 55/2sAbnormally fast request rate — automated scanning+35
Burst 57/2sAbnormally fast request rate — automated scanning+35
Burst 58/2sAbnormally fast request rate — automated scanning+35
Burst 59/2sAbnormally fast request rate — automated scanning+35
Burst 62/2sAbnormally fast request rate — automated scanning+35
Burst 63/2sAbnormally fast request rate — automated scanning+35
Burst 97/10sAbnormally fast request rate — automated scanning+35
Burst 98/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 10Medium-risk: admin panels, config files+60
Danger medium hits: 181Medium-risk: admin panels, config files+60
Danger medium hits: 184Medium-risk: admin panels, config files+60
Danger medium hits: 185Medium-risk: admin panels, config files+60
Danger medium hits: 186Medium-risk: admin panels, config files+60
Danger medium hits: 277Medium-risk: admin panels, config files+60
Danger medium hits: 278Medium-risk: admin panels, config files+60
Danger medium hits: 370Medium-risk: admin panels, config files+60
Danger medium hits: 372Medium-risk: admin panels, config files+60
Danger medium hits: 556Medium-risk: admin panels, config files+60
Danger medium hits: 73Medium-risk: admin panels, config files+60
Danger medium hits: 93Medium-risk: admin panels, config files+60
Danger strong hits: 109High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 120High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 158High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 218High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 26High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 60High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 76High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 79High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 3985
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-08-07 02:20:42
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst 102/10s (+35)
2026-08-16 01:04:04
Last malicious request observed
Total score reached: 280/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft
AS8075 · 🇨🇭 Switzerland
06

Recommendations

Actions taken & recommended

  • IP 172.161.1.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

🔎 Path Enumeration Protection

Block scanning from 172.161.1.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 172.161.1.105.

🤖 User-Agent Anomaly Defense

IP 172.161.1.105 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

172.161.1.105 has been assigned a threat score of 280/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 172.161.1.105, located in Zurich, Switzerland, operating on the network of Microsoft, has been classified as malicious by our automated threat scoring engine. The address has been active for 8 days in our monitoring system, producing 2,903 flagged requests at a rate of ~362.9/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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Our records show 12 malicious IPs originating from Switzerland, positioning it as a notable contributor to global threat activity. A score of 280/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.

11

Related Threats

🇨🇭 Top threats from Switzerland

20.203.179.12 (280)51.103.131.31 (280)20.203.183.135 (280)20.203.221.142 (280)20.203.200.218 (280)View all →

🏢 Same network: AS8075

68.155.155.199 (320)20.127.136.245 (318)20.151.200.44 (315)20.220.203.117 (280)20.79.30.30 (280)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Log Correlation and SIEM Integration

Correlating logs across web servers, firewalls, DNS, and authentication systems reveals attack patterns invisible in individual log sources. Modern SIEM platforms use statistical analysis to connect related events across time and systems.

🔍 Check Any IP Address

Share this report: