ABUSE.MOM
THREAT REPORT

IP Threat Report
146.19.175.14

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 03:39:37
First seen: 2026-02-19 09:00:06
Last seen: 2026-02-19 09:00:06
65

⛔ Verdict: BLOCK

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

BOT_UARATIO_404
01

Geolocation & Classification

IP Address
146.19.175.14
Type
Residential
Country
🇩🇪 Germany
City
Frankfurt am Main
ISP
trafficforce, UAB
Organization
Code200
Autonomous System
AS201341 trafficforce, UAB
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: crawlerKnown bot/crawler User-Agent detected+40
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Σ = 65
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-02-19 09:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: crawler (+40), 404 ratio >= 60% (+25)
2026-02-19 09:00:06
Last malicious request observed
Total score reached: 65/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

trafficforce, UAB
AS201341 · 🇩🇪 Germany
06

Recommendations

Actions taken & recommended

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

🤖 User-Agent Anomaly Defense

IP 146.19.175.14 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🔎 Directory Scan Defense

IP 146.19.175.14 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.

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

146.19.175.14 has been assigned a threat score of 65/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 146.19.175.14 to malicious activity originating from Frankfurt am Main, Germany, operating on the network of trafficforce, UAB. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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 Germany

View all →

🏢 Same network: AS201341

154.16.103.54 (90)154.16.103.245 (65)154.16.103.155 (65)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.

💡 Autonomous System Analysis

Analyzing attack patterns at the AS (Autonomous System) level reveals which networks harbor the most malicious activity. Some ASes have abuse rates orders of magnitude higher than average, indicating lax enforcement of acceptable use policies.

🔍 Check Any IP Address

Share this report: