ABUSE.MOM
THREAT REPORT

IP Threat Report
154.81.237.133

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-12 08:11:42
First seen: 2026-07-08 09:01:40
Last seen: 2026-07-12 00:55:48
95

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
154.81.237.133
Type
Mobile
Country
🇵🇰 Pakistan
City
Lahore
ISP
Pakistan Mobile Communications Limited
Organization
Pakistan Mobile Communications Limited
Autonomous System
AS45669 PMCL /LDI IP TRANSIT
Hit Count
325
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 5Medium-risk: admin panels, config files+50
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 95
03

Observed Activity

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

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

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

04

Timeline

2026-07-08 09:01:40
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 5 (+50), Foreign referer (+10)
2026-07-12 00:55:48
Last malicious request observed
Total score reached: 95/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Pakistan Mobile Communications Limited
AS45669 · 🇵🇰 Pakistan
06

Recommendations

Actions taken & recommended

  • IP 154.81.237.133 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 154.81.237.133: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

09

Blacklist Status (DNSBL)

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

✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net

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

10

Threat Analysis

154.81.237.133 has been assigned a threat score of 95/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 154.81.237.133, geolocated to Lahore, Pakistan, operating on the network of Pakistan Mobile Communications Limited, as a source of suspicious network activity. Our sensors captured 325 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~108.3 requests per day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 101 malicious IPs originating from Pakistan, positioning it as a significant contributor to global threat activity. At 95/100, this is an extremely high-risk address. All traffic should be considered hostile.

11

Related Threats

🇵🇰 Top threats from Pakistan

173.239.196.165 (255)173.239.196.167 (255)173.239.196.163 (255)173.239.196.161 (255)113.192.47.123 (240)View all →

🏢 Same network: AS45669

View all →
12

Security Intelligence

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

💡 Data Breach Impact Assessment

The impact of data breaches extends beyond immediate financial losses. Regulatory fines, legal liability, reputational damage, and customer churn create long-term costs that often exceed the direct costs of incident response and remediation.

🔍 Check Any IP Address

Share this report: