ABUSE.MOM
THREAT REPORT

IP Threat Report
31.22.104.251

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 00:18:05
First seen: 2026-06-28 14:47:23
Last seen: 2026-07-05 04:01:31
85

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
31.22.104.251
Type
Residential
Country
🇫🇮 Finland
City
Helsinki
ISP
DataCrunch Oy
Organization
Verda Cloud Oy
Autonomous System
AS198020 Verda Cloud Oy
Hit Count
634
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 85
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-06-28 14:47:23
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger strong hits: 2 (+50), Probe 302→404 (+20)
2026-07-05 04:01:31
Last malicious request observed
Total score reached: 85/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DataCrunch Oy
AS198020 · 🇫🇮 Finland
06

Recommendations

Actions taken & recommended

  • IP 31.22.104.251 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 31.22.104.0/24
  • 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 31.22.104.251 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

07

Neighbors in 31.22.104.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

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
b.barracudacentral.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 31.22.104.251 to malicious activity originating from Helsinki, Finland, operating on the network of DataCrunch Oy. The address has been under observation since its initial detection. During its 6-day observation window, we recorded 634 hostile requests from this IP — roughly 105.7 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. At 85/100, this IP warrants immediate defensive action.

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 Finland

View all →

🏢 Same network: AS198020

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.

💡 GeoIP Blocking Considerations

Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.

🔍 Check Any IP Address

Share this report: