ABUSE.MOM
THREAT REPORT

IP Threat Report
41.95.225.94

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 13:20:02
First seen: 2026-04-20 14:00:08
Last seen: 2026-04-20 14:00:08
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
41.95.225.94
Type
Mobile
Country
🇸🇩 SD
City
Khartoum
ISP
ZAIN SD 2G 3G LTE APN Internet
Organization
Unknown
Autonomous System
AS36998 Sudanese Mobile Telephone (ZAIN) Co Ltd
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 103
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-20 14:00:08
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), POST requests present (+8)
2026-04-20 14:00:08
Last malicious request observed
Total score reached: 103/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

ZAIN SD 2G 3G LTE APN Internet
AS36998 · 🇸🇩 SD
06

Recommendations

Actions taken & recommended

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

⚙️ General Security

Add 41.95.225.94 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

⛔ LISTED
zen.spamhaus.org
⛔ LISTED
b.barracudacentral.org
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

41.95.225.94 has been assigned a threat score of 103/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

📊 Threat Analysis

Network traffic from 41.95.225.94, located in Khartoum, SD, operating on the network of ZAIN SD 2G 3G LTE APN Internet, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. Our records show 12 malicious IPs originating from SD, positioning it as a notable contributor to global threat activity. With a threat score of 103/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

11

Related Threats

🇸🇩 Top threats from SD

41.95.239.250 (103)154.100.9.0 (103)154.100.9.51 (103)41.95.141.36 (103)102.120.188.227 (103)View all →

🏢 Same network: AS36998

41.95.239.250 (103)154.100.9.0 (103)154.100.9.51 (103)41.95.141.36 (103)41.95.234.104 (68)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: