ABUSE.MOM
THREAT REPORT

IP Threat Report
144.124.240.71

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:30:39
First seen: 2026-02-17 17:25:05
Last seen: 2026-02-19 06:00:07
300

⛔ Verdict: BLOCK

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

UA_CHANGEDDANGER_PATHRATIO_404REDIRECT_PROBEBURSTIMPORT
01

Geolocation & Classification

IP Address
144.124.240.71
Type
Hosting
Country
🇳🇱 Netherlands
City
Amsterdam
ISP
Servers Tech Fzco
Organization
Servers Tech Fzco
Autonomous System
AS216071 SERVERS TECH FZCO
Hit Count
5
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 21High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 15Medium-risk: admin panels, config files+60
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 27 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 27 req / 10sAbnormally fast request rate — automated scanning+35
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Burst: 21 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 335
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-17 17:25:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger strong hits: 21 (+100), Danger medium hits: 15 (+60)
2026-02-19 06:00:07
Last malicious request observed
Total score reached: 300/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Servers Tech Fzco
AS216071 · 🇳🇱 Netherlands
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

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

🔎 Path Enumeration Protection

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

🌊 Traffic Flood Defense

IP 144.124.240.71 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 (1)
PortServiceRiskDescription
3389RDPHighRemote Desktop Protocol — primary target for ransomware attacks

⚠️ 1 high-risk port detected on 144.124.240.71. Exposed RDP (3389) is the #1 entry point for ransomware attacks. These services should not be publicly accessible without strict firewall rules.

Hostnames: v634129.hosted-by-vdsina.com
PTR: v634129.hosted-by-vdsina.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.

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

144.124.240.71 has been assigned a threat score of 300/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

Network traffic from 144.124.240.71, located in Amsterdam, Netherlands, operating on the network of Servers Tech Fzco, has been classified as malicious by our automated threat scoring engine. The address has been active for 1 days in our monitoring system, producing 5 flagged requests at a rate of ~5/day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 102 flagged addresses, Netherlands represents a significant presence in our threat database. A score of 300/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇳🇱 Top threats from Netherlands

185.184.192.251 (338)45.88.138.44 (320)45.82.64.236 (315)5.181.169.192 (313)157.22.73.141 (313)View all →

🏢 Same network: AS216071

91.84.116.83 (300)144.124.246.157 (300)195.26.224.52 (300)194.164.33.148 (300)89.110.116.2 (280)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 Supply Chain Security Challenges

Attacks targeting software supply chains compromise trusted update mechanisms to distribute malware at scale. Dependency confusion, typosquatting in package registries, and compromised build pipelines threaten even organizations with strong direct security postures.

🔍 Check Any IP Address

Share this report: