ABUSE.MOM
THREAT REPORT

IP Threat Report
68.155.153.75

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-24 18:08:55
First seen: 2026-10-14 06:09:46
Last seen: 2026-10-18 00:10:00
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
68.155.153.75
Type
Hosting
Country
🇲🇽 Mexico
City
Querétaro City
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (mexicocentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
1110
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 17/2sAbnormally fast request rate — automated scanning+35
Burst 18/2sAbnormally fast request rate — automated scanning+35
Burst 57/10sAbnormally fast request rate — automated scanning+35
Burst 58/10sAbnormally fast request rate — automated scanning+35
Burst 59/10sAbnormally fast request rate — automated scanning+35
Burst 60/10sAbnormally fast request rate — automated scanning+35
Burst 61/10sAbnormally fast request rate — automated scanning+35
Burst 62/10sAbnormally fast request rate — automated scanning+35
Burst 63/10sAbnormally fast request rate — automated scanning+35
Burst 64/10sAbnormally fast request rate — automated scanning+35
Burst 65/10sAbnormally fast request rate — automated scanning+35
Burst 66/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 120Medium-risk: admin panels, config files+60
Danger medium hits: 158Medium-risk: admin panels, config files+60
Danger medium hits: 170Medium-risk: admin panels, config files+60
Danger medium hits: 172Medium-risk: admin panels, config files+60
Danger medium hits: 258Medium-risk: admin panels, config files+60
Danger strong hits: 16High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 22High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 1295
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-10-14 06:09:46
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 17/2s (+35), Burst 18/2s (+35)
2026-10-18 00:10:00
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 Corporation
AS8075 · 🇲🇽 Mexico

We have detected 1852 malicious IPs from this autonomous system.

View all IPs from AS8075 →
06

Recommendations

Actions taken & recommended

  • IP 68.155.153.75 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 68.155.153.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 68.155.153.75 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

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

🤖 Bot Detection

Address UA spoofing from 68.155.153.75: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 68.155.153.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

68.155.153.75 has been assigned a threat score of 280/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 68.155.153.75 has been traced to Querétaro City, Mexico, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 3 days, this IP generated 1,110 malicious requests, averaging approximately 370 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Mexico currently accounts for 280 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 280/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 Mexico

68.155.155.199 (320)158.23.144.198 (280)68.155.146.66 (280)68.155.145.150 (280)158.23.146.113 (280)View all →

🏢 Same network: AS8075

68.155.155.199 (320)20.127.136.245 (318)20.151.200.44 (315)20.92.77.159 (310)20.210.128.125 (310)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.

💡 IPv6 Scanning Challenges

The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.

🔍 Check Any IP Address

Share this report: