ABUSE.MOM
THREAT REPORT

IP Threat Report
154.80.2.11

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-10 09:06:20
First seen: 2026-07-31 13:18:20
Last seen: 2026-08-02 00:50:11
95

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
154.80.2.11
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
77
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-31 13:18:20
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-08-02 00:50:11
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.80.2.11 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

🔎 Directory Scan Defense

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

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
psbl.surriel.com
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

154.80.2.11 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.80.2.11, geolocated to Lahore, Pakistan, operating on the network of Pakistan Mobile Communications Limited, as a source of suspicious network activity. During its 1-day observation window, we recorded 77 hostile requests from this IP — roughly 77 per day on average. 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. With 103 flagged addresses, Pakistan represents a significant presence in our threat database. 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.167 (255)173.239.196.170 (255)173.239.196.162 (255)173.239.196.165 (255)173.239.196.169 (255)View all →

🏢 Same network: AS45669

154.81.237.133 (95)154.81.234.121 (95)View all →
12

Security Intelligence

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

💡 TLS Certificate Misconfigurations

Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.

🔍 Check Any IP Address

Share this report: