ABUSE.MOM
THREAT REPORT

IP Threat Report
103.8.26.89

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:56:59
First seen: 2026-02-18 10:00:06
Last seen: 2026-03-16 23:00:07
195

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404BURSTREFERER
01

Geolocation & Classification

IP Address
103.8.26.89
Type
Residential
Country
🇲🇾 MY
City
Subang Jaya
ISP
SKSATECH1
Organization
Unknown
Autonomous System
AS132241 SKSA TECHNOLOGY SDN BHD
Hit Count
22
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Burst: 30 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 30 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 26High-risk paths: shells, RCE vectors, exploits+100
Burst: 23 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 26 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 28High-risk paths: shells, RCE vectors, exploits+100
Burst: 21 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 28 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 27 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Burst: 10 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 10 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 26 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 1045
03

Observed Activity

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

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

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

04

Timeline

2026-02-18 10:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 12 (+100), 404 ratio 40-60% (+15), Burst: 12 req / 2s (+35)
2026-03-16 23:00:07
Last malicious request observed
Total score reached: 195/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

SKSATECH1
AS132241 · 🇲🇾 MY
06

Recommendations

Actions taken & recommended

  • IP 103.8.26.89 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 103.8.26.89 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

IP 103.8.26.89 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

08

Open Ports & Services

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

OPEN PORTS (16)
PortServiceRiskDescription
22SSHLowSecure Shell — common brute force target for remote access
26UnknownLowService on port 26
53DNSLowDNS server — potential for DNS amplification attacks
80HTTPLowHTTP web server — standard web traffic
110POP3LowService on port 110
111UnknownLowService on port 111
143IMAPLowService on port 143
443HTTPSLowHTTPS web server — encrypted web traffic
465UnknownLowService on port 465
587UnknownLowService on port 587
993IMAPSLowService on port 993
2082UnknownLowService on port 2082
2083UnknownLowService on port 2083
2086UnknownLowService on port 2086
2087UnknownLowService on port 2087
3306MySQLHighMySQL database — should never be exposed to the internet

⚠️ Network scanning reveals 1 dangerous service exposed on 103.8.26.89. These services should not be publicly accessible without strict firewall rules.

KNOWN VULNERABILITIES (CVE) (14)
CVE IDLink
CVE-2008-3844NVD →
CVE-2025-26465NVD →
CVE-2020-14145NVD →
CVE-2023-51767NVD →
CVE-2023-51385NVD →
CVE-2016-20012NVD →
CVE-2025-32728NVD →
CVE-2021-41617NVD →
CVE-2007-2768NVD →
CVE-2021-36368NVD →
CVE-2023-38408NVD →
CVE-2019-16905NVD →
CVE-2020-15778NVD →
CVE-2023-48795NVD →

🔴 Security scanning identified 14 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.

DETECTED TECHNOLOGIES
exim:exim:4.99.1apache:http_servercpanel:cpaneloracle:mysqlopenbsd:openssh:8.0
Hostnames: autoconfig.main.congresscatalyst.comwebdisk.main.congresscatalyst.comwhm.main.congresscatalyst.comcongresscatalyst.comcpcontacts.main.congresscatalyst.comcpcalendars.main.congresscatalyst.commain.congresscatalyst.comcpanel.main.congresscatalyst.comautodiscover.main.congresscatalyst.comipv6.main.congresscatalyst.comwebmail.main.congresscatalyst.comippk.enomba.infowww.main.congresscatalyst.commail.main.congresscatalyst.com
PTR: autoconfig.main.congresscatalyst.com

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
Spamhaus ZEN

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

10

Threat Analysis

103.8.26.89 has been assigned a threat score of 195/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

IP address 103.8.26.89 has been traced to Subang Jaya, MY, operating on the network of SKSATECH1. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 26 days, this IP generated 22 malicious requests, averaging approximately 0.8 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. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 101 malicious IPs originating from MY, positioning it as a significant contributor to global threat activity. A score of 195/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 MY

173.239.236.80 (305)101.99.94.104 (265)173.239.236.211 (255)173.239.236.71 (255)173.239.236.44 (255)View all →

🏢 Same network: AS132241

103.8.27.27 (230)103.8.25.126 (105)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.

💡 Patch Management Urgency

The window between vulnerability disclosure and exploitation continues to shrink. Critical CVEs are now exploited within hours of publication. Automated patch management, virtual patching through WAFs, and rapid deployment pipelines are essential for timely remediation.

🔍 Check Any IP Address

Share this report: