ABUSE.MOM
THREAT REPORT

IP Threat Report
74.162.69.29

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:13:46
First seen: 2026-03-02 08:00:04
Last seen: 2026-03-04 08:00:06
170

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404REFERER
01

Geolocation & Classification

IP Address
74.162.69.29
Type
Hosting
Country
🇦🇪 AE
City
Dubai
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (uaenorth)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
5
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 23High-risk paths: shells, RCE vectors, exploits+100
Burst: 18 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 23 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Foreign referer seenReferer from unrelated external domain+10
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Σ = 295
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-02 08:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 23 (+100), Burst: 18 req / 2s (+35), Burst: 23 req / 10s (+35)
2026-03-04 08:00:06
Last malicious request observed
Total score reached: 170/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇦🇪 AE
06

Recommendations

Actions taken & recommended

  • IP 74.162.69.29 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.162.69.29 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.162.69.29: 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 (5)
PortServiceRiskDescription
21FTPMediumFile Transfer Protocol — often targeted for anonymous login attacks
443HTTPSLowHTTPS web server — encrypted web traffic
995POP3SLowService on port 995
2082UnknownLowService on port 2082
2087UnknownLowService on port 2087

⚠️ Network scanning reveals 1 dangerous service exposed on 74.162.69.29. These services should not be publicly accessible without strict firewall rules.

DETECTED TECHNOLOGIES
pureftpd:pure-ftpdcpanel:whmapache:http_server
Hostnames: lps.projectsutility.comwww.lps.projectsutility.com74-162-69-29.cprapid.comserver.projectsutility.com
PTR: lps.projectsutility.com

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.

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

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

Request FloodingPath Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 74.162.69.29 to malicious activity originating from Dubai, AE, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Our sensors captured 5 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~2.5 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 AE, positioning it as a significant contributor to global threat activity. A score of 170/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 AE

74.243.251.125 (280)86.98.32.142 (168)172.86.76.182 (165)156.244.211.9 (140)92.97.157.211 (135)View all →

🏢 Same network: AS8075

74.243.251.125 (280)View all →
12

Security Intelligence

💡 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.

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

🔍 Check Any IP Address

Share this report: