ABUSE.MOM
THREAT REPORT

IP Threat Report
68.155.154.218

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:43:39
First seen: 2026-03-29 12:00:05
Last seen: 2026-03-29 13:00:07
255

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

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

Detection Signatures

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

Network Provider

Microsoft Corporation
AS8075 · 🇲🇽 Mexico
06

Recommendations

Actions taken & recommended

  • IP 68.155.154.218 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.154.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 68.155.154.218.

🔎 Directory Scan Defense

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

07

Neighbors in 68.155.154.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.

⛔ LISTED
zen.spamhaus.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

68.155.154.218 has been assigned a threat score of 255/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

Threat intelligence analysis has linked 68.155.154.218 to malicious activity originating from Querétaro City, Mexico, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 5 hostile requests from this IP — roughly 5 per day on average. 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 (Request Flooding and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 122 flagged addresses, Mexico represents a significant presence in our threat database. At 255/100, this is an extremely high-risk address. All traffic should be considered hostile.

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

158.23.144.198 (280)68.155.145.150 (280)68.155.146.66 (280)34.51.104.11 (263)104.243.245.4 (255)View all →

🏢 Same network: AS8075

158.23.144.198 (280)68.155.145.150 (280)68.155.146.66 (280)68.155.154.154 (255)158.23.176.117 (245)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.

💡 IoT Device Compromise Patterns

Internet of Things devices are prime targets for botnet recruitment due to weak default credentials, infrequent updates, and always-on connectivity. Compromised IoT devices generate persistent scanning and attack traffic without their owners knowledge.

🔍 Check Any IP Address

Share this report: