ABUSE.MOM
THREAT REPORT

IP Threat Report
109.70.100.9

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-29 16:10:41
First seen: 2026-02-19 01:27:52
Last seen: 2026-05-29 16:03:29
73

⛔ Verdict: BLOCK

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

BOT_UABURSTDANGER_PATHFORM_SPAMMETHODRATIO_404REFERERUA_SUS
01

Geolocation & Classification

IP Address
109.70.100.9
Type
Residential
Country
🇦🇹 Austria
City
Vienna
ISP
Foundation for Applied Privacy
Organization
Foundation Applied Privacy
Autonomous System
AS208323 Foundation for Applied Privacy
Hit Count
932
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst: 19 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Foreign refererReferer from unrelated external domain+10
Form spam: no_js_checkSpam/malware keywords in request content+0
POST seenBehavioral anomaly detected by automated analysis+8
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 218
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-19 01:27:52
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst: 19 req / 10s (+35), Burst: 6 req / 2s (+35)
2026-05-29 16:03:29
Last malicious request observed
Total score reached: 73/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Foundation for Applied Privacy
AS208323 · 🇦🇹 Austria
06

Recommendations

Actions taken & recommended

  • IP 109.70.100.9 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 109.70.100.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

Block scanning from 109.70.100.9: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Traffic Flood Defense

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

📧 Spam Protection

Enable CAPTCHA on all public forms. Add honeypot fields. Rate-limit submissions to 3 per minute per IP. Deploy Akismet or CleanTalk.

🤖 Bot Detection

Address UA spoofing from 109.70.100.9: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 109.70.100.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
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

109.70.100.9 has been assigned a threat score of 73/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 EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

The address 109.70.100.9 originates from Vienna, Austria, operating on the network of Foundation for Applied Privacy. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 932 malicious requests from this address across a 99-day span, reflecting a sustained attack cadence of ~9.4 requests per day. 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 61 flagged addresses, Austria represents a notable presence in our threat database. At 73/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 Austria

45.95.243.145 (280)45.95.243.132 (280)87.249.133.67 (255)87.249.133.18 (255)89.187.168.57 (255)View all →

🏢 Same network: AS208323

109.70.100.12 (100)109.70.100.7 (100)109.70.100.4 (100)109.70.100.2 (100)109.70.100.11 (100)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Botnet Command and Control Evolution

Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.

🔍 Check Any IP Address

Share this report: