ABUSE.MOM
THREAT REPORT

IP Threat Report
110.38.226.66

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:26:34
First seen: 2026-04-11 02:00:08
Last seen: 2026-04-29 04:00:06
115

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGEDDANGER_PATHUA_SUS
01

Geolocation & Classification

IP Address
110.38.226.66
Type
Residential
Country
🇵🇰 Pakistan
City
Lahore
ISP
Wateen Telecom Limited
Organization
Wateen Telecom Limited
Autonomous System
AS38264 National WiMAX/IMS environment
Hit Count
7
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: curlKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
UA bot: pythonKnown bot/crawler User-Agent detected+40
UA bot: okhttpKnown bot/crawler User-Agent detected+40
Σ = 210
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-04-11 02:00:08
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: curl (+40), UA changed for same IP (+25), Danger strong hits: 2 (+50)
2026-04-29 04:00:06
Last malicious request observed
Total score reached: 115/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Wateen Telecom Limited
AS38264 · 🇵🇰 Pakistan
06

Recommendations

Actions taken & recommended

  • IP 110.38.226.66 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

🤖 Bot Detection

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (2)
PortServiceRiskDescription
1723PPTPLowService on port 1723
4444UnknownLowService on port 4444
Hostnames: GPONUser38226-66.wateen.net
PTR: GPONUser38226-66.wateen.net

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
dnsbl-1.uceprotect.net
⛔ LISTED
zen.spamhaus.org
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

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

User-Agent Anomaly

📊 Threat Analysis

110.38.226.66 is registered in Lahore, Pakistan, operating on the network of Wateen Telecom Limited. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 18 days, this IP generated 7 malicious requests, averaging approximately 0.4 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. Pakistan currently accounts for 122 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 115/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇵🇰 Top threats from Pakistan

113.192.47.123 (240)182.184.118.5 (235)173.239.196.170 (225)202.142.146.84 (210)103.84.56.36 (208)View all →

🏢 Same network: AS38264

58.27.215.2 (168)110.39.134.98 (130)110.39.13.203 (103)110.37.18.68 (103)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 Memory Safety and Buffer Overflows

Buffer overflow vulnerabilities remain relevant in C/C++ applications despite decades of mitigation efforts. Modern protections like ASLR, stack canaries, and DEP reduce exploitability but determined attackers continue finding bypass techniques.

🔍 Check Any IP Address

Share this report: