ABUSE.MOM
THREAT REPORT

IP Threat Report
102.254.35.37

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 17:19:56
First seen: 2026-09-15 17:54:26
Last seen: 2026-09-20 02:10:45
60

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
102.254.35.37
Type
Mobile
Country
🇿🇦 South Africa
City
Pretoria
ISP
Telkom SA Ltd.
Organization
Telkom SA Ltd
Autonomous System
AS37457 Telkom SA Ltd.
Hit Count
149
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-09-15 17:54:26
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-09-20 02:10:45
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

Telkom SA Ltd.
AS37457 · 🇿🇦 South Africa

We have detected 18 malicious IPs from this autonomous system.

View all IPs from AS37457 →
06

Recommendations

Actions taken & recommended

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

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

10

Threat Analysis

102.254.35.37 has been assigned a threat score of 60/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Network traffic from 102.254.35.37, located in Pretoria, South Africa, operating on the network of Telkom SA Ltd., has been classified as malicious by our automated threat scoring engine. Over a period of 4 days, this IP generated 149 malicious requests, averaging approximately 37.3 requests per day. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 260 malicious IPs originating from South Africa, positioning it as a significant contributor to global threat activity. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

11

Related Threats

🇿🇦 Top threats from South Africa

94.156.152.43 (340)94.156.152.15 (305)34.35.175.130 (298)34.35.86.234 (298)34.35.171.47 (288)View all →

🏢 Same network: AS37457

105.186.193.24 (103)105.224.32.76 (103)105.224.25.190 (103)105.224.22.62 (93)102.254.69.27 (83)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 Automated Incident Response

Automated response systems can block threats in milliseconds, far faster than human analysts. However, automation requires careful safeguards — rate limits on blocking actions, automatic expiration, and human review queues prevent automated systems from causing self-inflicted outages.

🔍 Check Any IP Address

Share this report: