ABUSE.MOM
THREAT REPORT

IP Threat Report
173.44.138.79

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-05 05:26:10
First seen: 2026-06-07 03:39:07
Last seen: 2026-07-05 04:01:48
130

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
173.44.138.79
Type
Unknown
Country
🇩🇪 Germany
City
Frankfurt am Main
ISP
Eonix Corporation
Organization
Eonix Corporation
Autonomous System
Unknown
Hit Count
1613
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Danger medium hits: 4Medium-risk: admin panels, config files+40
Directory ScanBehavioral anomaly detected by automated analysis+0
Foreign refererReferer from unrelated external domain+10
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-07 03:39:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), DDoS / Flood, Danger medium hits: 4 (+40)
2026-07-05 04:01:48
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 173.44.138.79 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 173.44.138.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

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

07

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

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

10

Threat Analysis

173.44.138.79 has been assigned a threat score of 130/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

IP address 173.44.138.79 has been traced to Frankfurt am Main, Germany, operating on the network of Eonix Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 1,613 malicious requests from this address across a 28-day span, reflecting a sustained attack cadence of ~57.6 requests per day. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 103 flagged addresses, Germany represents a significant presence in our threat database. A score of 130/100 places this address in the top tier of severity. Block and investigate any historical connections.

11

Related Threats

🇩🇪 Top threats from Germany

15.220.152.241 (320)35.246.204.221 (320)185.168.29.98 (313)77.81.65.244 (313)91.217.249.222 (305)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.

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

🔍 Check Any IP Address

Share this report: