ABUSE.MOM
THREAT REPORT

IP Threat Report
105.168.134.147

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-06 02:41:42
First seen: 2026-08-11 01:14:19
Last seen: 2026-08-16 01:00:26
60

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
105.168.134.147
Type
Mobile
Country
🇦🇴 AO
City
Luanda
ISP
UNITEL SA
Organization
UnitelMobileCustomerPool1
Autonomous System
AS37119 UNITEL SA
Hit Count
190
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Foreign refererReferer from unrelated external domain+10
Σ = 60
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-08-11 01:14:19
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger strong hits: 1 (+25), Foreign referer (+10)
2026-08-16 01:00:26
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

UNITEL SA
AS37119 · 🇦🇴 AO
06

Recommendations

Actions taken & recommended

  • IP 105.168.134.147 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 105.168.134.147: 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
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

105.168.134.147 has been assigned a threat score of 60/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

IP address 105.168.134.147 has been traced to Luanda, AO, operating on the network of UNITEL SA. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 190 malicious requests from this address across a 4-day span, reflecting a sustained attack cadence of ~47.5 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 26 flagged addresses, AO represents a notable presence in our threat database. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

11

Related Threats

🇦🇴 Top threats from AO

105.174.17.50 (145)105.168.175.155 (103)105.174.59.178 (103)196.249.229.22 (103)102.220.192.174 (103)View all →

🏢 Same network: AS37119

105.174.17.50 (145)105.172.114.11 (60)105.168.44.104 (60)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.

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