ABUSE.MOM
THREAT REPORT

IP Threat Report
74.242.171.175

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 06:42:15
First seen: 2026-03-07 06:00:05
Last seen: 2026-03-07 08:00:05
180

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 19Medium-risk: admin panels, config files+60
Burst: 18 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 10sAbnormally fast request rate — automated scanning+35
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 15 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 17 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 20 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 20 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 16 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 14 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 530
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-03-07 06:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 1 (+25), Danger medium hits: 19 (+60), Burst: 18 req / 2s (+35)
2026-03-07 08:00:05
Last malicious request observed
Total score reached: 180/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇨🇭 Switzerland
06

Recommendations

Actions taken & recommended

  • IP 74.242.171.175 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

🌊 Traffic Flood Defense

IP 74.242.171.175 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🔎 Path Enumeration Protection

Block scanning from 74.242.171.175: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (1)
PortServiceRiskDescription
3389RDPHighRemote Desktop Protocol — primary target for ransomware attacks

⚠️ 1 high-risk port detected on 74.242.171.175. Exposed RDP (3389) is the #1 entry point for ransomware attacks. These services should not be publicly accessible without strict firewall rules.

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

74.242.171.175 has been assigned a threat score of 180/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:

Request FloodingPath Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 74.242.171.175, geolocated to Zurich, Switzerland, operating on the network of Microsoft Corporation, as a source of suspicious network activity. Our sensors captured 67 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~67 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Request Flooding combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. Our records show 101 malicious IPs originating from Switzerland, positioning it as a significant contributor to global threat activity. With a threat score of 180/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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

51.107.69.151 (280)20.250.10.152 (280)20.203.180.135 (280)20.203.136.132 (280)20.203.129.217 (280)View all →

🏢 Same network: AS8075

74.241.249.229 (340)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)20.29.71.103 (283)View all →
12

Security Intelligence

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

🔍 Check Any IP Address

Share this report: