ABUSE.MOM
THREAT REPORT

IP Threat Report
102.22.162.121

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:48:17
First seen: 2026-03-04 13:00:04
Last seen: 2026-03-04 13:00:04
93

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404METHOD
01

Geolocation & Classification

IP Address
102.22.162.121
Type
Residential
Country
🇷🇼 RW
City
Kigali
ISP
GVA Rwanda
Organization
GVA Rwanda Ltd
Autonomous System
AS36924 GVA Cote d'Ivoire SAS
Hit Count
1
02

Detection Signatures

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

Network Provider

GVA Rwanda
AS36924 · 🇷🇼 RW
06

Recommendations

Actions taken & recommended

  • IP 102.22.162.121 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.22.162.121 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.

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

102.22.162.121 has been assigned a threat score of 93/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

102.22.162.121 is registered in Kigali, RW, operating on the network of GVA Rwanda. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. At 93/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 RW

102.22.143.17 (68)View all →

🏢 Same network: AS36924

102.64.154.229 (133)102.64.219.191 (103)102.64.152.114 (103)102.64.154.17 (103)41.75.72.21 (93)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.

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

🔍 Check Any IP Address

Share this report: